You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MITM: Allow using local received SNI in the outgoing serverName & verifyPeerCertInNames
#4348 (comment)
Local received SNI was sent by browser/app.
In freedom RAW's `tlsSettings`, set `"serverName": "fromMitm"` to forward it to the real website.
In freedom RAW's `tlsSettings`, set `"verifyPeerCertInNames": ["fromMitm"]` to use all possible names to verify the certificate.
Copy file name to clipboardexpand all lines: transport/internet/tls/config.proto
+9-7
Original file line number
Diff line number
Diff line change
@@ -69,16 +69,14 @@ message Config {
69
69
70
70
boolreject_unknown_sni=12;
71
71
72
-
/* @Document A pinned certificate chain sha256 hash.
73
-
@Document If the server's hash does not match this value, the connection will be aborted.
74
-
@Document This value replace allow_insecure.
72
+
/* @Document Some certificate chain sha256 hashes.
73
+
@Document After normal validation or allow_insecure, if the server's cert chain hash does not match any of these values, the connection will be aborted.
/* @Document A pinned certificate public key sha256 hash.
80
-
@Document If the server's public key hash does not match this value, the connection will be aborted.
81
-
@Document This value replace allow_insecure.
78
+
/* @Document Some certificate public key sha256 hashes.
79
+
@Document After normal validation (required), if the verified cert's public key hash does not match any of these values, the connection will be aborted.
/* @Document Replaces server_name to verify the peer cert.
90
+
@Document After allow_insecure (automatically), if the server's cert can't be verified by any of these names, pinned_peer_certificate_chain_sha256 will be tried.
0 commit comments