Closed
Bug 1102589
Opened 10 years ago
Closed 5 years ago
refactor the relationship between nsSiteSecurityService and PublicKeyPinningService
Categories
(Core :: Security: PSM, defect, P5)
Core
Security: PSM
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: keeler, Unassigned)
References
Details
(Whiteboard: [psm-cleanup])
nsSiteSecurityService calls into PublicKeyPinningService to determine the validity of new HPKP (i.e. dynamic) pins. PublicKeyPinningService calls into nsSiteSecurityService when verifying certificate chains to see if a site has any dynamic pins.
We should sort out this circular dependency. My thinking at the moment is that it makes the most sense to put all of the functionality in nsSiteSecurityService and have that be a single entry-point for any external uses of it.
|
Reporter | |
Updated•9 years ago
|
Whiteboard: [psm-cleanup]
|
|
Reporter | |
Updated•7 years ago
|
Priority: -- → P5
|
|
Reporter | |
Comment 1•5 years ago
|
||
As of bug 1630038 the relationship between these two is less intricate.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•