Bug#642314: [Pkg-openssl-devel] Bug#642314: Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2013-06-10 Thread Thijs Kinkhorst
Hi Kurt, So I would like to drop the patch, but cacert.org.pem still contains 2 cert files. Michael, could you please consider splitting that file? A version of ca-certificates that spits cacert.org.pem has just been accepted into unstable. Cheers, Thijs -- To UNSUBSCRIBE, email to

Bug#642314: [Pkg-openssl-devel] Bug#642314: Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2012-09-09 Thread Kurt Roeckx
On Mon, Jul 30, 2012 at 01:38:30PM -0500, Michael Shuler wrote: On 07/29/2012 07:53 AM, Kurt Roeckx wrote: On Thu, Sep 22, 2011 at 10:15:50AM +0200, Loïc Minier wrote: Just thought of another minor issue with the new c_rehash handling multiple certs in the same file: when a piece of

Bug#642314: [Pkg-openssl-devel] Bug#642314: Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2012-07-30 Thread Michael Shuler
On 07/29/2012 07:53 AM, Kurt Roeckx wrote: On Thu, Sep 22, 2011 at 10:15:50AM +0200, Loïc Minier wrote: Just thought of another minor issue with the new c_rehash handling multiple certs in the same file: when a piece of software follows the hashed symlink, the certificate it's looking for

Bug#642314: [Pkg-openssl-devel] Bug#642314: Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2012-07-29 Thread Kurt Roeckx
On Thu, Sep 22, 2011 at 10:15:50AM +0200, Loïc Minier wrote: Just thought of another minor issue with the new c_rehash handling multiple certs in the same file: when a piece of software follows the hashed symlink, the certificate it's looking for might not be the first one. Is this

Bug#642314: Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-09-22 Thread Loïc Minier
Just thought of another minor issue with the new c_rehash handling multiple certs in the same file: when a piece of software follows the hashed symlink, the certificate it's looking for might not be the first one. Is this verified to work with gnutls and openssl implementations? I wonder

Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-09-21 Thread Loïc Minier
Hi The patch from Debian #628780 caused a regression with certificates using CRLF line-endings, which prompted me to take a look at the discussion here. (Debian #642314 is the regression.) Outside of CRLF line-endings, there seems to be potential for more regressions in this patch:

Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-09-21 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Loïc and others, lets address the comment in the right order not in the order of severity. Am Mi den 21. Sep 2011 um 14:49 schrieb Loïc Minier: The patch from Debian #628780 caused a regression with certificates using CRLF line-endings,

Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-09-21 Thread Loïc Minier
On Wed, Sep 21, 2011, Klaus Ethgen wrote: Hmm.. I think, certificates on unix with CRLF line ending is broken and should be fixed. You mean people should not use CRLF in their certificates when running Debian? Or you mean we should fix support for CRLF in certificates? I have absolutely no

Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-06-01 Thread Klaus Ethgen
And a last version of my patch that also handles clean the duplicated certs. (ca-certificates.crt is always a problem but do not handle special in this patch.) Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen

Bug#628780: Wrong hash link to cacert.org.pem and wron certificat hash handling at all

2011-06-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: ca-certificates Version: 20110421 Severity: important The current links to the cacert.org.pem are 5ed36f99.0 and 99d0fa06.0. Thie first certificate in that file is correct 99d0fa06.0 but the second certificate hash is 590d426f.0 _not_