Closed Bug 476070 Opened 16 years ago Closed 2 months ago

After accepting SSL certificate exception on new account, password dialog does not pop up

Categories

(Thunderbird :: Security, defect)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: erase, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090129 Shredder/3.0b2pre similar to bug 322145, resubmitting as that one is two years old with no action. -create a new account for a server with a self-signed SSL certificate. -set account to use SSL -click on inbox for account -a warning pops up, asking to confirm an SSL exception -confirm the exception -thunderbird "spins", claiming it is trying to connect, but has no password for the account and will sit there indefinitely expected result: password dialog should pop up after confirming the security exception. workaround: click on another mailbox (or local folder), then back on inbox for the ssl account. the password dialog will pop up this time. Reproducible: Always Steps to Reproduce: 1- create a new account for a server with a self-signed SSL certificate. 2- set account to use SSL 3- click on inbox for account - a warning pops up, asking user to confirm an SSL exception 4- confirm the exception Actual Results: thunderbird "spins", claiming it is trying to connect, but has no password for the account and will sit there indefinitely Expected Results: password dialog should pop up after confirming the security exception. workaround: click on another mailbox (or local folder), then back on inbox for the ssl account. the password dialog will pop up this time.
Component: General → Security
QA Contact: general → thunderbird
note: also happens when sending mail for the first time - having to accept the SSL certificate causes the password dialog to be skipped and the message fails to send. on the next attempt to send the password dialog pops up and everything works correctly.
Severity: minor → S3

I can't imagine this still exists.

Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.