Re: SHA-1 collision in repository?

2018-02-23 Thread Branko Čibej
On 24.02.2018 01:09, Myria wrote: > Once it's on my local machine, I'll be able to compile TortoiseSVN and > debug it while pointing to a file:// repository. (TortoiseSVN instead > of command-line svn because TortoiseSVN is compiled with Visual C++ > and is therefore many times easier to debug.)

Re: SHA-1 collision in repository?

2018-02-23 Thread Philip Martin
Philip Martin writes: > There are a couple of options: > > A) disable rep-caching by editing fsfs.conf inside the repository > > B) reset the mapping by deleting/renaming the file db/rep-cache.db > inside the repository (but please rename rather than delete if you > want to help us

Re: SHA-1 collision in repository?

2018-02-23 Thread Philip Martin
Myria writes: > I was able to branch (svn copy) the affected branch to a new branch, > and committing the same file to the new branch has the same error. > Checking out that revision works fine; only that commit is affected. I suspect the problem is that the repository revision files are OK but

Re: SHA-1 collision in repository?

2018-02-23 Thread Myria
On Fri, Feb 23, 2018 at 2:50 PM, Philip Martin wrote: > Stefan Sperling writes: > > I think this might be the case since you mentioned earlier that you > could not find a file with the given checksum. The checksums apply to > the repository format, i.e. before keyword/eol transformation, and if

Re: SHA-1 collision in repository?

2018-02-23 Thread Philip Martin
Stefan Sperling writes: > On Fri, Feb 23, 2018 at 01:06:36PM -0800, Myria wrote: >> The revision 605556 is simply the current revision number of the >> repository at the time of the attempted commit, and is unrelated to >> the problem. If I attempt the commit now, it's a higher number, but >> ot

Re: SHA-1 collision in repository?

2018-02-23 Thread Stefan Sperling
On Fri, Feb 23, 2018 at 01:06:36PM -0800, Myria wrote: > I'm not subscribed to this mailing list, so I have no standard way to > reply to Philip's email. I don't even know his email address. > > > That pattern, all of MD5, SHA1 and size matching, is exactly what > > happens if a SHA1 collision is

Re: SHA-1 collision in repository?

2018-02-23 Thread Myria
I'm not subscribed to this mailing list, so I have no standard way to reply to Philip's email. I don't even know his email address. > That pattern, all of MD5, SHA1 and size matching, is exactly what > happens if a SHA1 collision is committed using an old version of > Subversion where the rep-cac