Re: [fossil-users] Is Fossil Hash-collision proof?

2017-03-22 Thread Richard Hipp
On 3/22/17, Scott Robison wrote: > > Let's say for the sake of argument that you somehow wind up with two > modified files in the same commit that have the same hash but different > contents. Fossil will read back the data it just wrote to ensure what went > into the repo

Re: [fossil-users] Is Fossil Hash-collision proof?

2017-03-22 Thread Scott Robison
On Mar 21, 2017 11:04 PM, "Martin Vahi" wrote: I haven't encountered any collisions yet, but I was wondering, what will happen, if 2 different files that have the same size, same timestamps, different bitstreams, but the same hash (regardless of hash algorithm) were to

Re: [fossil-users] Is Fossil Hash-collision proof?

2017-03-21 Thread Warren Young
On Mar 21, 2017, at 11:04 PM, Martin Vahi wrote: > > I haven't encountered any collisions yet Nor are you likely to by accident, ever. The only reason it’s even a concern is that a motivated attacker with lots of money could force a collision with the old SHA-1

[fossil-users] Is Fossil Hash-collision proof?

2017-03-21 Thread Martin Vahi
I haven't encountered any collisions yet, but I was wondering, what will happen, if 2 different files that have the same size, same timestamps, different bitstreams, but the same hash (regardless of hash algorithm) were to be committed simultaneously, at the same commit? After all, it's the