Re: SHA-1 collision in repository?

2018-03-07 Thread Myria
000: >> Myria wrote on Mon, Feb 26, 2018 at 13:41:05 -0800: >> > In other news, unknown whether related to the current problem, my >> > attempt to clone the repository to my local computer is failing: >> > >> > D:\>svnsync sync

Re: SHA-1 collision in repository?

2018-03-07 Thread Myria
expanded_size to zero: representation_t next_rep = { 0 }; Does the code just need this? I don't know this call >.< next_rep.expanded_size = rb->rep.expanded_size; Melissa On Wed, Mar 7, 2018 at 9:02 AM, Nathan Hartman wrote: > On Mar 5, 2018, at 10:54 PM, Myria wrote: >

Re: SHA-1 collision in repository?

2018-03-05 Thread Myria
;size; first_rep->size is 16384, and this is why rb->len becomes 16384, leading to the error. I don't know what all this code is doing, but that's the proximate cause of the failure. Melissa On Mon, Mar 5, 2018 at 7:41 PM, Myria wrote: > When Subversion gets to this part of rep_

Re: SHA-1 collision in repository?

2018-03-05 Thread Myria
ere hash='e6291ab119036eb783d0136afccdb3b445867364'" e6291ab119036eb783d0136afccdb3b445867364|227170|153|193|57465 On Mon, Mar 5, 2018 at 6:56 PM, Myria wrote: > GMail keeps doing reply instead of reply all. I'm having to manually > add the users list back now. > > Below is the threa

Fwd: SHA-1 collision in repository?

2018-03-05 Thread Myria
GMail keeps doing reply instead of reply all. I'm having to manually add the users list back now. Below is the thread I sent. -- Forwarded message -- From: Myria Date: Mon, Mar 5, 2018 at 6:37 PM Subject: Re: SHA-1 collision in repository? To: Philip Martin I now know

Re: SHA-1 collision in repository?

2018-03-04 Thread Myria
How can I dump out the two things that Subversion thinks have the same SHA-1 checksum but don't match? This seems to be rather difficult to do. That said, it's far more likely that there's a bug in Subversion than that we randomly collided SHA-1. On Sun, Mar 4, 2018 at 02:29 Philip Martin wrote

Re: SHA-1 collision in repository?

2018-03-02 Thread Myria
The problem is identical on Windows command line, Windows TortoiseSVN, Ubuntu-Linux, Ubuntu-Linux on Windows, and macOS. I'm just bad at GDB. On Thu, Mar 1, 2018 at 9:09 PM, Nico Kadel-Garcia wrote: > On Thu, Mar 1, 2018 at 10:25 PM, Myria wrote: >> I just found out that the fi

Re: SHA-1 collision in repository?

2018-03-01 Thread Myria
how to proceed is to wait until the source code to TortoiseSVN is available so that I can debug it in Visual Studio. Is there something else I can do? On Thu, Mar 1, 2018 at 6:45 PM, Myria wrote: > On Wed, Feb 28, 2018 at 6:17 AM, Nico Kadel-Garcia wrote: >> On Tue, Feb 27, 2018

Re: SHA-1 collision in repository?

2018-03-01 Thread Myria
On Wed, Feb 28, 2018 at 6:17 AM, Nico Kadel-Garcia wrote: > On Tue, Feb 27, 2018 at 4:09 PM, Myria wrote: > >> Not to mention that the two revisions complained about are unrelated, and >> 2/3 the repository history apart. >> >> One thing that's interesting is

Re: SHA-1 collision in repository?

2018-02-27 Thread Myria
On Tue, Feb 27, 2018 at 05:54 Philip Martin wrote: > Myria writes: > > > -bash-4.1$ sqlite3 rep-cache.db "select * from rep_cache where > > hash='db11617ef1454332336e00abc311d44bc698f3b3'" > > db11617ef1454332336e00abc311d44bc698f3b3|604440|34|134

Re: SHA-1 collision in repository?

2018-02-26 Thread Myria
-bash-4.1$ sqlite3 rep-cache.db "select * from rep_cache where hash='db11617ef1454332336e00abc311d44bc698f3b3'" db11617ef1454332336e00abc311d44bc698f3b3|604440|34|134255|136680 The line from the grep -a command containing that hash is below. They all match. text: 604440 34 134255 136680 c9f4fabc4

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 Myria
Could the collision be in a "diff" instead of the files themselves? Melissa On Thu, Feb 22, 2018 at 2:45 PM, Matt Simmons wrote: > I would get more advice from people here before you invest that time. I'm a > relative amateur and would listen to people with more experience th

Re: SHA-1 collision in repository?

2018-02-22 Thread Myria
> > > On Thu, Feb 22, 2018 at 12:30 PM, Myria wrote: >> >> When we try to commit a very specific version of a very specific >> binary file, we get a SHA-1 collision error from the Subversion >> repository: >> >> D:\confidential>svn commit secret.bin

SHA-1 collision in repository?

2018-02-22 Thread Myria
When we try to commit a very specific version of a very specific binary file, we get a SHA-1 collision error from the Subversion repository: D:\confidential>svn commit secret.bin -m "Testing broken commit" Sendingsecret.bin Transmitting file data .svn: E16: Commit failed (details follo