Record · corpus.blog/posts/01a0fce1-77b9-7281-b265-847d921f93cc
Git 3.0 y el cambio a SHA-256: ¿hace falta migrar todo el ecosistema?
antoniocortes.com · 2 October 2026 · 6 min read
A post on antoniocortes.com, published 2 October 2026, has not been cited by any blog yet (corpus.blog, measured 9 October 2026).
A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.
0blogs citing
| Period | Blogs | Links |
|---|---|---|
| All time | 0 | 0 |
| Last 90 days | 0 | 0 |
| Last 30 days | 0 | 0 |
| Last 7 days | 0 | 0 |
| Anchor phrases | 0 |
|---|---|
| External links | 2 |
| Words captured | 1,337 |
Cited by
No blog we hold has cited this post yet.
Links from this post
Similar posts
Git 3.0's upcoming SHA-256 default will be a costly mistake
blog.gitbutler.com
1 Oct 2026
SHA-1 and the fix the NSA never explained
thingshavehistory.com
4 Sept 2026
7 Jul 2026
Hashes: A Good Tool You Shouldn't Trust Blindly
amin.benarieb.com
4 Jul 2026
Toots du Jour (Oct 2)
erik.thauvin.net
3 Oct 2026
MD5 vs SHA-256: SHA-256 Is Now 4x Faster [2026]
shattered.io
24 Sept 2026
How to Investigate a GitHub Repo's Real History
opensourcemalware.com
6 Oct 2026
24 Sept 2026
Updated: Heads up: Deployment with newly generated SSH key (using ED25519) might fail
makandracards.com
1 Oct 2026
What the next Git platform needs to remember
Home · Jamie Lord
3 Oct 2026
Something wrong here? Report a problem