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

No patch releases though, right?

    http://svn.apache.org/repos/asf/subversion/trunk/CHANGES

Is that because, "the server can store the offending PDFs" isn't enough of
a releasable in its own right? Or because the "the server can store the
offending PDFs" specifically is imperfect and unreleasable in some way?

- Paul

On Thu, Mar 30, 2017 at 4:42 AM, Stefan Sperling <stsp_at_elego.de> wrote:

> On Thu, Mar 30, 2017 at 09:30:57AM +0100, Julian Foad wrote:
> > Hi, devs. Re. the SHA-1 fixes contemplated or in-the-works for SVN 1.8
> and
> > 1.9: Any idea on how those are coming along and when they might see the
> > light of day (in patch releases)?
> >
> > - Julian
> >
>
> As far as I can tell, these changes touch FSFS only. So while the server
> can now store the offending PDF files, nothing has been done yet regarding
> other areas which have problems with these files such as the working copy
> (pristine store) and ra_serf (avoids fetching files already stored in
> pristine store).
>
> And perhaps there are more areas which have problems? I am not aware
> of any effort to figure that out.
>
Received on 2017-03-30 12:01:59 CEST