Certificate exceptions sometimes not found

RESOLVED DUPLICATE of bug 659736

Status

()

Core
Security
RESOLVED DUPLICATE of bug 659736
8 years ago
5 years ago

People

(Reporter: Siyivan, Unassigned)

Tracking

(Depends on: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090510 Firefox/3.6a1pre

When accessing a page with a self-signed certificate for which an exception has been added, _sometimes_ firefox 'forgets' the exception and show "This connection is untrusted message".
When going to readd it, it's remembered and you're not allowed to add the exception (so it's not that the exception were deleted from the store).

See attached screenshot.

Workaround: Choose to add the exception, get firefox to realise it knows the certificate, cancel window, reload https page.


Reproducible: Always
(Reporter)

Comment 1

8 years ago
Created attachment 376723 [details]
Untrusted certificate and valid certificate at the same time
(Reporter)

Comment 2

8 years ago
Created attachment 376724 [details]
Untrusted certificate and valid certificate at the same time
Attachment #376723 - Attachment is obsolete: true

Comment 3

6 years ago
This issue is still in Firefox 7.0.1 (Windows 7 64 bit). Please deliver a fix.
When you've added a permanent exception for a self-signed certificate this is sometimes forgotten at random times. The page that the certificate is self-signed is shown

Comment 4

6 years ago
and when you want to add the exception again it shows that the certificate is valid, yet you can't continue and you can't add the exception. The only way to quickly solve it is by killing firefox.exe.

Possibly related or the same:
https://bugzilla.mozilla.org/show_bug.cgi?id=524500
https://bugzilla.mozilla.org/show_bug.cgi?id=457573

Comment 5

6 years ago
I don't what the issue was in 2009.

The additional issue described in 2011 sounds like a dupe of 660749.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 660749
Let's see whether the fix for bug 660749 fixes this issue, before we mark that it is a duplicate.
Status: RESOLVED → REOPENED
Depends on: 660749
Ever confirmed: true
Resolution: DUPLICATE → ---
(Reporter)

Comment 7

6 years ago
What was "added" in 2011? The content of comment 4? You can even view it in the screenshot how the button to add the exception was disabled.

Niels, did you test the workaround that I mentioned?

I'm not sure the fix for bug 660749 would fix it other than by chance when touching related code. It is for "trusting less" stored certificates, this is due to "not trusting enough" (not finding the cert).
The "valid and invalid at the same time" issue is now bug 659736.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 659736
You need to log in before you can comment on or make changes to this bug.