Re: SHA-1 collision in repository?

On Sun, Mar 04, 2018 at 11:12:00AM +0000, Philip Martin wrote:
> Stefan Sperling <stsp_at_elego.de> writes:
>
> > Yes. And if the content differs, it must be rejected, because an FSFS
> > repository can only store one content per SHA1 checksum.
>
> To be accurate the server-side code can handle the files perfectly well
> if rep-caching is disabled.

Yes, that's true. But turning the rep-cache off is *not* recommended.

> The on the client side the working copy code doesn't handle the files as
> the pristines collide.

The network protocol over HTTP will have problems as well: ra_serf won't
fetch files it believes the working copy already has in the pristine store.
Received on 2018-03-04 12:37:50 CET