Closed
Bug 1531958
Opened 7 years ago
Closed 7 years ago
make http2 test certificates more consistent with existing test certificate infrastructure
Categories
(Core :: Networking, enhancement, P1)
Core
Networking
Tracking
()
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: keeler, Assigned: keeler)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Right now the http2 xpcshell test certificates are inconsistent with other xpcshell test certificates in that there is no in-tree way to regenerate them should they expire (currently this is handled by having them be valid until 2027). We can use the existing test certificate infrastructure (pycert/pykey) to make this easier. As a bonus, it allows us to remove an unnecessary use of nsIBadCertListener2.
|
Assignee | |
Comment 1•7 years ago
|
||
This patch uses the existing xpcshell test certificate infrastructure
(pycert/pykey) to manage the http2 test certificates (and gets rid of some uses
of nsIBadCertListener2 as a bonus).
|
||
Updated•7 years ago
|
Whiteboard: [necko-triaged]
Pushed by dkeeler@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f2f2c1e2c322
make http2 test certificates more consistent with existing test certificate infrastructure r=dragana
|
|
||
Comment 3•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in
before you can comment on or make changes to this bug.
Description
•