-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS client protocol does not seem to be properly set from config #280
Comments
The tls_client config here only affect https_forward requests. Currently we don't support set outgoing tls protocol versions in tls interception. |
To support custom TLS client config for HTTP CONNECT requests, you need to use user-site config. user-group:
- name: default
anonymous_user:
name: anonymous
audit:
enable_protocol_inspection: true
explicit_sites:
- id: browserleaks
exact_match: browserleaks.com
tls_client:
protocol: tls1.2 And you need to change the |
Thanks! I will give it a try. Does it require setting explicit sites or can it be used across all? |
It only work for the matched sites. |
Could this be a feature request in the future? Thanks! |
It's possible but I'm wondering whether it's really needed for all tls connections. |
We use it to match certain browser configs - similar to #138. |
You can set max/min tls version after this commit e9b41b6 |
I am trying to set the tls client protocol for outgoing requests (that are intercepted) the value does not appear to be respected. For example I set it to tls1.2 but when I test with https://browserleaks.com/tls it always shows 1.3. This happens with openssl and boringssl. Example config:
The text was updated successfully, but these errors were encountered: