292584 - thunderbird 1.0.2 doesn't notify that a cert has expired

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Jason Haar]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Hi

I use a client cert to connect to our IMAP server. The cert expired and instead
of being notified (well, I expected to be notified ;-) via a popup that the
current IMAPS connection won't work as the cert is expired, thunderbird started
connecting *without* the client cert! That then got rightly rejected by the
server and I got a popup error about being unable to connect to the IMAP server
and perhaps I should up the max number of TCP connection allowed per server -
totally irrelevent to the problem.

The IMAPS server was reporting an SSL error that the client wasn't sending a cert:

SSL_accept: error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not
return a certificate

..so that's why I feel it's thunderbird acting up.


Reproducible: Always




I then removed the expired cert and added my new one back in and restarted
thunderbird - problem solved as expected.

Comment 1

[Thomas K. (:tom)]

This seems to be dependant on Bug 274970.  Marking as such.

Also, Bug 258159 says that there is a certificate expired message, but it's
slightly broken.

Comment 2

[Jason Haar]

I don't think it is. That other cert problem is related to S/MIME isn't it? I'm
referring to TLS client certificates as part of a secure IMAP-over-SSL connection.

Jason

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.