Re: SHA-1 collision in repository?

On Mar 4, 2018, at 5:28 AM, Stefan Sperling <stsp_at_elego.de> wrote:
>
>> On Sat, Mar 03, 2018 at 09:08:41PM -0500, Nathan Hartman wrote:
>> Does this mean that content being committed to the repository is never elided
>> based on the SHA hash alone but only after a fulltext verification that the
>> content actually already exists in the repository?
>
> Yes. And if the content differs, it must be rejected, because an FSFS
> repository can only store one content per SHA1 checksum.

Just a thought here: perhaps in Myria's case no collision was ever stored, but rather one of the repository's files on disk became corrupt for some reason. Bit rot? Bad disk sector? Now it doesn't match its SHA sum and throws an error when trying to commit a file that is identical to the one committed previously but which doesn't match the fulltext of that earlier commit because of the bit rot / corruption.
Received on 2018-03-04 13:48:35 CET