Open Bug 1415312 Opened 8 years ago Updated 1 year ago

Make CT SCTs available to the certificate error page.

Categories

(Core :: Security: PSM, enhancement, P3)

Product:
Core
Component:
Security: PSM
Type:
enhancement

Tracking

()

Milestone:
Future

People

(Reporter: jcj, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [psm-backlog])

In order to give the error analysis code the same context as Mozilla::PKIX, we need to also provide the Certificate Transparency SCT that was used when determining the error. One place to put that response might be nsISSLStatus, where the certificate chain is stored. [1] http://searchfox.org/mozilla-central/source/security/manager/ssl/nsISSLStatus.idl

FYI, this may or may not be more work than cutting Firefox over to using something like Certainly Something:

https://github.com/april/certainly-something

Which parses certs in JavaScript to display the SCTs.

Severity: normal → S3

This bug seems has been fixed? Test this: https://no-sct.badssl.com

While Firefox (on desktop) requires CT, the error page doesn't include SCTs in the debugging information it shows, which is the issue this bug is describing.

Severity: S3 → N/A
Priority: P2 → P3
Whiteboard: [psm-backlog]
You need to log in before you can comment on or make changes to this bug.