Skip to content

Latest commit

 

History

History
19 lines (14 loc) · 1.13 KB

tq-021-TLS-cert-recording.md

File metadata and controls

19 lines (14 loc) · 1.13 KB

tq-021 TLS cert recording

Every TLS connection observing certificate validation anomalies should record the full certificate as injection of self-signed certificate is another method for transparency of TLS-based protocols censorship. Failure to validate a certificate should be recorded, but should not block the connection as some ISPs serve blockpages for HTTPS URLs that way.

OONI Probe may prefer to ship it’s own CA bundle to avoid trusting “enterprise” CAs in “enterprise” networks on BYOD devices running OONI Probe.

TLS1.3 will require certificate being exported from TLS library as TLS1.3 encrypts it on the wire.

TBD: it’s unclear if TLS certificates recording should be always-on feature.

TBD: it's unclear if we should or should not submit to CertificateTransparency logs without understanding if the issuing CA is Locally-trusted “enterprise” CA or not. It may be non trivial to implement while shipping our own CA bundle.