Closed Bug 492054 Opened 16 years ago Closed 13 years ago

Expire entries from nsPSMRememberCertErrorsTable::mErrorHosts hash table

Categories

(Core :: Security: PSM, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: mayhemer, Unassigned)

References

Details

(Whiteboard: [MemShrink])

We store for each certificate that has some errors like domain name mismatch an entry to mErrorHosts hast table. We may by time bloat this table and keep already expired information that has to be kept only for time of the client SSL session remains valid. Thus, we should expire those entries from time to time. This feature has been implemented in bug 445871 that is 1.9.1 blocking. We should decide if this should come to 1.9.1 as well.
Flags: wanted1.9.1?
Flags: wanted1.9.1?
Good first bug.
Assignee: honzab.moz → nobody
Assignee: nobody → joshmoz
Whiteboard: [MemShrink]
Each entry in the table is a struct containing three bool values. The entries are only stored when there is a cert error (rarely), and if the error ever clears up they are removed. I'll leave this bug open but I'm not going to work on it now as the memory cost is very minor.
Assignee: joshmoz → nobody
Whiteboard: [MemShrink] → [MemShrink:P3]
AFAICT, this is not worth tracking for MemShrink. If this is coming up often, it is most likely because users are running into bogus cert errors (i.e. false positives) and we should fix *that*. Otherwise, this will be extremely unlikely to bloat things. Realistically, we will not ever have enough time to implement any optimizations for the cert error case. Re-open if you disagree.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Whiteboard: [MemShrink:P3] → [MemShrink]
We marked it MemShrink:P3 because it's a small, rare leak. WONTFIXing seems reasonable to me.
You need to log in before you can comment on or make changes to this bug.