Open
Bug 1281469
Opened 8 years ago
Updated 3 months ago
Implement Certificate Transparency support (RFC 6962)
Categories
(Core :: Security: PSM, task, P3)
Core
Security: PSM
Tracking
()
NEW
People
(Reporter: sergei.cv, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [psm-tracking])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
|
Reporter | |
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [psm-tracking]
Depends on: 1313511
|
||
Comment 1•7 years ago
|
||
Related Talk about RFC 6962 - https://www.youtube.com/watch?v=4GQLvogFGO4&list=PLOcrXzpA0W82Z49Pj0v-cehuvA9qCDuX9&index=4 ietf Ref: https://tools.ietf.org/html/rfc6962
|
||
Updated•4 years ago
|
Type: defect → task
|
||
Updated•2 years ago
|
Severity: normal → S3
Should this bug be closed due to the feature being deprecated?
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT
Note: The Expect-CT is mostly obsolete since June 2021. Since May 2018, all new TLS certificates are expected to support SCTs by default. Certificates issued before March 2018 were allowed to have a lifetime of 39 months, so they had expired in June 2021. Chromium plans to deprecate Expect-CT header and to eventually remove it.
No - "Expect-CT" (the HTTP header) is not the same thing as CT (the general feature).
| Comment hidden (advocacy) |
| Comment hidden (off-topic) |
You need to log in
before you can comment on or make changes to this bug.
Description
•