forked from lwthiker/curl-impersonate
-
-
Notifications
You must be signed in to change notification settings - Fork 108
Open
Labels
Description
using profile chrome136.
I've got a site that uses http3 and sits behind CF.
libcurl-impersonate fails the fingerprint unless i force tls13 only via CURLOPT_SSL_VERSION = TLSv1_3.
the default is tls12 | MAX which does tls13 with tls12 fallback.
i think what is happening is that the initial http3 handshake used a different (tls13 specific) cipher suite and forcing TLSv13 actually just uses the default curl tls13 cipher suite which happens to pass the fingerprint check.
curl has CURLOPT_TLS13_CIPHERS but it fails NOT_BUILT_IN if i try to use it to.
my thought is that probably the impersonate profile could use a .tls13_ciphers field that gets passed to CURLOPT_TLS13_CIPHERS so that http3 initiated sessions can be easily used.
Reactions are currently unavailable