Open
Bug 1359743
Opened 7 years ago
Updated 2 years ago
Create production test entries for dynamic STS and PKP preloads
Categories
(Toolkit :: Blocklist Implementation, enhancement)
Toolkit
Blocklist Implementation
Tracking
()
NEW
People
(Reporter: mgoodwin, Unassigned)
Details
It would be useful to have something akin to pinning-test.badssl.com or the old pinningtest.appspot.com that allows us to test production data relating to the dynamic preload mechanisms for STS and PKP. For each of these, we'd need a real (mozilla) FQDN pointing to an actual host. In the STS case, this should have some configuration disallowed by HSTS (e.g. no TLS or a bad certificate). In the PKP case, there should be a good certificate chain. The STS preload entry should just enable STS for the STS host (including sub-domains is not necessary). The PKP preload entry should have an incorrect pinset for the chain served by the PKP test host.
Updated•6 years ago
|
Component: Blocklist Policy Requests → Blocklist Implementation
Comment 1•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: bugs → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•