Re: Files with identical SHA1 breaks the repo

2017-03-02 Thread Garance A Drosehn
On 2 Mar 2017, at 6:37, Daniel Shahaf wrote: Garance A Drosehn wrote on Wed, Mar 01, 2017 at 14:48:07 -0500: I do not see how this extended-sha1 would be easier to break than the current sha1, because it includes the current sha1, unchanged. Regarding "easier to break", you wer

Re: Files with identical SHA1 breaks the repo

2017-03-01 Thread Garance A Drosehn
On 1 Mar 2017, at 7:18, Daniel Shahaf wrote: > Stefan Sperling wrote on Wed, Mar 01, 2017 at 11:01:40 +0100: >> On Tue, Feb 28, 2017 at 10:17:34PM -0600, Greg Stein wrote: >>> I really like this idea. >>> >>> And we could take a copy of APR's sha1 code, and rejigger >>> it to perform *both* hashes

Re: Files with identical SHA1 breaks the repo

2017-02-26 Thread Garance A Drosehn
On 24 Feb 2017, at 15:46, Stefan Sperling wrote: > > I believe we should prepare a new working format for 1.10.0 > which addresses this problem. I don't see a good way of fixing > it without a format bump. The bright side of this is that it > gives us a good reason to get 1.10.0 ready ASAP. > > We

Re: Low level of activity

2017-02-07 Thread Garance A Drosehn
On 6 Feb 2017, at 3:58, Stefan Sperling wrote: > On Sun, Feb 05, 2017 at 07:21:21PM +, Daniel Shahaf wrote: >> Stefan Sperling wrote on Sat, Feb 04, 2017 at 20:03:36 +0100: >>> You may have gotten used to a level of activity which was made >>> possible by several full-time employment positions