446176 - Permanently Store Exception doesn't

Status: RESOLVED WORKSFORME

(Core :: Security: PSM, defect)

Description

[Colin Ogilvie [:cso]]

Every time I'm presented with an invalid security certificate, I tell it to permanently store the exception (it's a local box, and I know the certificate is 'valid' for the box).

However, ever time I revisit the same page, the same warning comes up and the box is still ticked... so it would appear permanently storing the exception isn't working.

Comment 1

[Matthias Versen [:Matti]]

The box for permanently storing is enabled by default.
Are you sure that the box presents you always the same certificta ?
Or are you accessing it with localhost ?

Comment 2

[Colin Ogilvie [:cso]]

The certificate hasn't changed in a number of months... 

It's accessed using something other than localhost, and in a variety of circumstances - either through a proxy server or not, on different machines, with different sites and different certificates.

Comment 3

[Daniel Veditz [:dveditz]]

Are you accessing it consistently with the same name (likely, but need to be sure)? The "exception" ties the particular cert to a particular host name; hitting through different IP addresses or proxies should work just fine, but accessing it as a different name won't.

If you're using the same name it's possible the exception database has gotten corrupted (or maybe it's read-only?). Kai may want to look at it for clues to what might be going wrong so if you do decide to delete it please save a copy somewhere if you don't mind.

Comment 4

[Colin Ogilvie [:cso]]

Consistently the same hostname, yeah.

I'm not actually sure where it is to delete so if you let me know I'll save a copy of it off, delete it and try again.

Comment 5

[Johnathan Nightingale [:johnath]]

Colin - bug 436870 tracked the fact that firefox 3.0 would tend to lose certificate exceptions after a certain number were added - we've fixed that in Firefox 3.0.1 - can you get the upgrade and tell us if you still see the problem?

Comment 6

[Colin Ogilvie [:cso]]

Hmm, seems to be working now in 3.0.1 -- but that's what I was using when I reported the bug.

Since this now seems to be working for me, I'm going to resolve WORKSFORME