Certificate in authorities cache not been updated ( automatically )

RESOLVED WONTFIX

Status

()

Core
Security: PSM
RESOLVED WONTFIX
10 years ago
2 years ago

People

(Reporter: Sandro Valentini, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

The FF isn't automatically updating certificates at cache authorities.

We need to enter in tools -> certificate manager -> authorities , and then delete the expired certificate by hand. 

This is quite a hard task to a simple user.



Reproducible: Always

Steps to Reproduce:
1. Have a certificate expired in authorities cache of FF.
2. Try to enter in a site that uses that certificate ( by sure, up to date )
3. You will receive a error that the certificate is expired, but is not. The expired is the certificate in cache authorities of FF.
Actual Results:  
1. Have a certificate expired in authorities cache of FF.
2. Try to enter in a site that uses that certificate ( by sure, up to date )
3. You will receive a error that the certificate is expired, but is not. The expired is the certificate in cache authorities of FF.
(Reporter)

Comment 1

10 years ago
Created attachment 355584 [details]
Evidence
-> PSM - dunno if it's valid or not, but the cert caching (I thought it was just intermediates?) is managed below the Firefox layer
Assignee: nobody → kaie
Component: Security → Security: PSM
Product: Firefox → Core
QA Contact: firefox → psm

Comment 3

8 years ago
Mass change owner of unconfirmed "Core:Security UI/PSM/SMime" bugs to nobody.
Search for kaie-20100607-unconfirmed-nobody
Assignee: kaie → nobody
Firefox doesn't automatically update expired root certificates.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.