Closed Bug 836400 Opened 11 years ago Closed 11 years ago

CRLs with duplicate names do not get autoupdated (or displayed as autoupdated)

Categories

(Core :: Security: PSM, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cviecco, Unassigned)

References

Details

Attachments

(1 file)

CRLs are identified in the prefs by their Organizational Unit (OU). This makes CRLS with the same OU (and distinct url) not to be autoupdated when they exist in the database.

I have not confirmed if the CRL is actually updated and is just the CRL display is out of sync.

To reproduce: 
Import:
http://evsecure-crl.verisign.com/EVSecure2006.crl
and then:
http://evsecure-crl.verisign.com/pca3-g5.crl

Open the Revocation List UI: you will notice two Verisign Trust Network CRLs

Leave for a week and notice that first CRL is not being updated.
see also bug 282945 comment 18 ff. (perhaps it should be dup'ed to that one)
OS: Linux → All
Hardware: x86_64 → All
The CRL Manager / Revocation Lists feature was removed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: