Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-09-01 Thread subs
I just encountered this problem with a newly built wheezy laptop. An upgrade to libnss 3.15.1-1 appears to fix it. Now when I set a new email account the advanced tab is available where before it was greyed out and add exceptions for self signed certs. I got the files from

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Philonous Atio
On Sun, 24 Mar 2013 22:00:17 -0400, Daniel Kahn Gillmor wrote: can you give more details about your platform and the version used? I am running Debian Wheezy with Xfce (fully up to date as of 23 Mar 2013) software on a desktop computer with an AMD Athlon 64 X2 3800+ processor, Asus A8N5X

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Daniel Kahn Gillmor
Hi Philonous-- On 03/24/2013 08:40 AM, Philonous Atio wrote: Perhaps my phrasing was not quite clear, but the remote server's certificate was NOT loaded into the Authorities section -- I wanted to avoid the need to load the server's certificate at all. I meant to convey that a self-signed

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Daniel Kahn Gillmor
On 03/23/2013 09:38 PM, Philonous Atio wrote: I agree with dkg that this sounds to me like a bug in the logic of the upgraded version of NSS. It needs to be fixed Please read the rest of my comments in this bug, Philonous -- i think you should have the remote server's certificate loaded in

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Philonous Atio
On Sun, 24 Mar 2013 01:41:34 -0400, Daniel Kahn Gillmor wrote: i think you should have the remote server's certificate loaded in your Servers tab, not in your Authorities tab. Perhaps my phrasing was not quite clear, but the remote server's certificate was NOT loaded into the Authorities

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Philonous Atio
On Sun, 24 Mar 2013 18:33:54 -0400, Daniel Kahn Gillmor wrote: In X.509, ... Thank you for the mini-tutorial on terminology. The certificates I am concerned about in this bug are regular EE certificates. Using MD5 for X.509 signatures of intermediate CAs and EE certificates has been a bad

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Daniel Kahn Gillmor
On 03/24/2013 08:41 PM, Philonous Atio wrote: But with libnss3 2:3.14.3-1, on my system Icedove did not complete the connection (it hung) and issued no message. hm, i see what you mean. Maybe #703587 should be reassigned to icedove (or cloned, and the clone reassigned to icedove). I'd do that

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-25 Thread Daniel Kahn Gillmor
On 03/24/2013 11:05 PM, Philonous Atio wrote: ||/ Name Version Architecture +++-==-- ii icedove10.0.12-1i386 ii libnss3:i386 2:3.14.3-1 i386 Thanks for these details. I can confirm the same misbehavior of icedove

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-23 Thread Philonous Atio
I had the same problem as Erik C.J. Laan, the original poster. My CA certificate is imported into the Authorities section of Icedove's certificates, but I have imported no other certificates. This setup has been working for a long time in Debian and it works on Thunderbird in Windows.

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-22 Thread Daniel Kahn Gillmor
On Thu 2013-03-21 10:28:31 -0400, Daniel Kahn Gillmor wrote: The self-signed certificate in question uses RSA-MD5 as a signature. MD5 is deprecated in general, so I suspect this is the problem. You could probably even re-generate the same self-signed certificate with the same key using SHA1

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-21 Thread Erik C.J. Laan
Package: libnss3 Version: 2:3.14.3-1 Severity: important Dear Maintainer, * What led up to the situation? I upgraded libnss* from 2:3.13.6-2 (previously in wheezy) to 2:3.14.3-1 (new in wheezy). Suddenly Icedove cannot connect to my IMAP-mail server anymore. That mail-server has a

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-21 Thread Erik C.J. Laan
I have some additional information: The error messages in detail. The Icedove error message when StartTLS is selected is: The IMAP server accountname does not support the selected authentication method. Please change the 'Authentication method' in the 'Account Settings | Server Settings'.

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-21 Thread Daniel Kahn Gillmor
On 03/21/2013 01:43 AM, Erik C.J. Laan wrote: I upgraded libnss* from 2:3.13.6-2 (previously in wheezy) to 2:3.14.3-1 (new in wheezy). Suddenly Icedove cannot connect to my IMAP-mail server anymore. That mail-server has a self-signed certificate. Thunderbird on other PCs (Win7) does not

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-21 Thread Erik C.J. Laan
On 03/21/13 15:28, Daniel Kahn Gillmor wrote: On 03/21/2013 01:43 AM, Erik C.J. Laan wrote: I upgraded libnss* from 2:3.13.6-2 (previously in wheezy) to 2:3.14.3-1 (new in wheezy). Suddenly Icedove cannot connect to my IMAP-mail server anymore. That mail-server has a self-signed certificate.

Bug#703587: libnss3 update disables some (self signed) certs (with Icedove)

2013-03-21 Thread Erik C.J. Laan
On 03/21/2013 07:46 PM, Erik C.J. Laan wrote: On 03/21/13 15:28, Daniel Kahn Gillmor wrote: On 03/21/2013 01:43 AM, Erik C.J. Laan wrote: I upgraded libnss* from 2:3.13.6-2 (previously in wheezy) to 2:3.14.3-1 (new in wheezy). Suddenly Icedove cannot connect to my IMAP-mail server anymore.