[reportlab-users] Reportlab SVN repository inaccessible via https with recent svn/neon versions
jtk at yahoo.com
Tue Nov 17 16:31:15 EST 2009
Robin Becker <robin <at> reportlab.com> writes:
> Jeff Kowalczyk wrote:
> > Jeff Kowalczyk <jtk <at> yahoo.com> writes:
> >> The reportlab SVN repository is inaccessible via https for users
> >> with recent versions of neon, a dependency of subversion.
> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548773
> >> Debian Bug report logs - #548773
> >> [libneon27-gnutls] authentication to subversion via https fails
> >> with "Insecure Algorithm" error
> > Could someone at RL take a look at this?
> > Thanks,
> > Jeff
> Our server also works in http: so that should fix your problems wrt md5/trust
> etc etc. Not sure exactly why we advertise everything in https, we use
> https for checking in though. Up to now https hasn't been a problem.
So it does, thanks. I just confirmed that an http checkout works fine:
$ svn co http://svn.reportlab.com/svn/public/reportlab/trunk reportlab
Previous messages to this group indicated that RL's ISP was not forwarding port
80 to the server, and for that reason HTTPS checkouts were necessary for all (at
Regarding the underlying issue, it appears that the certificate will need to be
remade, that is all. The recent versions of libneon et. al. reject MD5 signed
certificates as a matter of policy. The bug above indicated that they weren't
inclined to provide an override for the user.
More information about the reportlab-users