[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Progress on SHA-1 fixes in patch releases?

From: Stefan Fuhrmann <stefan2_at_apache.org>
Date: Mon, 17 Apr 2017 22:17:46 +0200

On 30.03.2017 21:38, Daniel Shahaf wrote:
> Let's use jira or moinmoin to track all the different issues that need
> looking into? I count at least fsfs, fsx, svnadmin load, libsvn_wc, and
> zhakov's change that Bert mentioned.

What is the problem with 'svnadmin load'?

It uses SHA1 and MD5 to verify that the data is valid
but will not detect intended changes that transformed
the dump stream from one valid / consistent state to
another. Apart from that, the FS backend should now
handle collisions just fine.

With FSFS and FSX fixed in /trunk (FSX not with the
backport IMO), there is only the wc issue left. Not sure
how much efficiency we want to sacrifice there. For
instance, switching between branches will become
expensive again.

-- Stefan^2.
Received on 2017-04-17 22:17:59 CEST

This is an archived mail posted to the Subversion Dev mailing list.