Make sure the HPKP/HSTS preload expiration dates are accurate for Firefox 60

RESOLVED FIXED in Firefox 60

Status

()

enhancement
P1
normal
RESOLVED FIXED
Last year
Last year

People

(Reporter: lizzard, Assigned: jcristau)

Tracking

60 Branch
mozilla60
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox60blocking fixed)

Details

Attachments

(1 attachment, 1 obsolete attachment)

+++ This bug was initially created as a clone of Bug #1412331 +++

Confirm and patch security/manager/ssl/StaticHPKPins.h and security/manager/ssl/nsSTSPreloadList.inc in 60 to have sufficient lifetime on the preloaded HPKP and STS pins.

Going off past precedents, we'll want an expiration date of around 2018-08-21 to coincide with the release of Firefox 62 (though that date should be confirmed closer to the time of landing the patch in case of schedule changes).
Summary: Make sure the HPKP/HSTS preload expiration dates are accurate for Firefox 59 → Make sure the HPKP/HSTS preload expiration dates are accurate for Firefox 60
No longer depends on: 1412331
Assignee

Comment 1

Last year
Note to future-self: based on a 62 release on 2018-08-21 this should land on beta60 after 2018-04-10.
Assignee

Comment 2

Last year
Posted patch bug1436376-expirations.patch (obsolete) — Splinter Review
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Assignee

Comment 3

Last year
Moved the expiration date to new planned 62 release date (September 5)
Attachment #8958508 - Attachment is obsolete: true
Attachment #8967774 - Flags: review?(jjones)
Comment on attachment 8967774 [details] [diff] [review]
bug1436376-expirations-v2.patch

Review of attachment 8967774 [details] [diff] [review]:
-----------------------------------------------------------------

I agree, this is 5 September. :)
Attachment #8967774 - Flags: review?(jjones) → review+
Assignee

Comment 5

Last year
https://hg.mozilla.org/releases/mozilla-beta/rev/d61d89ee46dc1cdcad74c6292124f1e25449178d
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in before you can comment on or make changes to this bug.