-
Notifications
You must be signed in to change notification settings - Fork 100
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
Using SSLproxy to downgrade TLS 1.3 to TLS1.2 #63
Comments
*SSLProto rules in global, proxyspec, and filterrules config apply to both client and server sides. So I don't think SSLproxy can do that. But, I think that may happen if client or server chooses different protocols, which is not under your control. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello
Is it possible to use SSLproxy in the following scenario:
The downgrade objective is to use a URL filter that supports only TLS 1.2
client ---(TLS1.3/1.2)-- SSLproxy ----(TLS1.2)--URLF --(TLS1.2)----server
(I read somewhere that this is actually an attack and that TLS1.3 has some defense mechanism for it, so may be I'm just hoping)
If the answer is yes, do you have an idea about how much traffic can SSLproxy can handle in this scenario?
Omar
The text was updated successfully, but these errors were encountered: