Rendered at 03:16:44 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
KolmogorovComp 3 hours ago [-]
Does it mean that when switching trop sha1 to sha256 you need to forcepush and rewrite all history? Wouldn’t that be a massive source of potential vulnerabilities?
infogulch 15 minutes ago [-]
Couldn't you write something that checks every commit's content and message is byte equal to the old tree? One scan through the history to verify it should be relatively simple if not cheap. Should be built into git.
em-bee 2 hours ago [-]
i guess that for now only the default will change for new repositories. support for sha1 is not going to be dropped, so most existing repositories won't switch any time soon. if you want to switch then yes, it sounds like a force push might be needed, although it could also be that simply switching is not possible, but that instead you have to create a new repo and import the history from the old repo, forcing everyone to clone the new repo intentionally.
nomel 3 hours ago [-]
I don't know much about this. How does that enable vulnerabilities exactly?
jayd16 3 hours ago [-]
Trusting a forced push w/o any other verification means nefarious history changes can be slipped in.
vlovich123 13 minutes ago [-]
You can still verify the contents - the content blobs don’t change after the migration. Not sure if there’s a practical attack one could do but maybe