I think this is fixed in neon27 version 0.29.6-3 and SVN isn't the only
thing affected by this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/576750
Title:
SVN client does not work due to Certif
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: neon27 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/576750
Title:
SVN
** Changed in: neon27 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/576750
Title:
SVN client does not work due to Certificate verification error
To m
Solved only with the downgrade of libneon27-gnutls.
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
It does not work here ...
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Here's a quick work around while you wait for certificates to be updated
etc.
Add to the end of your ~/.subversion/servers file:
ssl-trust-default-ca = no
more write up here:
http://jamescrisp.org/2010/06/05/workaround-for-subversion-svn-certificate-verification-error-insecure-algorithm-on-ubun
As mentioned by Marco, not a bug in subversion.
** Package changed: subversion (Ubuntu) => neon27 (Ubuntu)
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I agree. Given the massive amount of certs out there signed with MD5, I
think it's a bad move to just suddenly start rejecting them en-masse,
especially without any real description of why that is in the error
messages generated by the applications. There should at least be some
sort of workaround
** Tags added: patch
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
I made a small patch to neon that re-enables MD5, fixed my local problem.
A polite way to go about this would mean creating a config / policy file
somewhere, perhaps under GnuTLS itself.
** Patch added: "neon27-tls_md5.patch"
http://launchpadlibrarian.net/48257262/neon27-tls_md5.patch
--
SVN
Bug looks to be appearing when trying to connect to repository with
HTTPS when repo does not have signed and trusted certificate. On repos
with signed SSL cert bug does not seem to occur.
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You
The issue is not in subversion but under the package:
libneon27-gnutls
So I created a package with karmic version for lucid, should fix your issue,
but remind that this is not a real bug, but more certificates that should be
recreated.
http://www.marcocimmino.net/2010/05/05/libneon27-gnutls_0-28
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47972464/Dependencies.txt
--
SVN client does not work due to Certificate verification error
https://bugs.launchpad.net/bugs/576750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
13 matches
Mail list logo
