-
Notifications
You must be signed in to change notification settings - Fork 242
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
Adds support for HTTPS(TLS-in-TLS) proxies and fixes incorrect regex #457
base: main
Are you sure you want to change the base?
Conversation
…ncorrectly parsing `procotol://username:password@hostname:port/`, it will not work for passwords/usernames that contain `@`, `:`, or whitespace.
Hey! I tried to check all default proxy lists with |
@monosans bizarre, when you say "any proxies" do you mean specifically https or even http? If it's the former it's likely that the public https proxies are using self signed certificates that aren't able to be verified by the SSL context. HTTPS proxies are very useful for ensuring that the proxy server can't easily mess with the confidentiality between client -> target host when proxying. If you modify PROXY_SSL_CONTEXT = ssl.create_default_context(cafile=certifi.where())
PROXY_SSL_CONTEXT.check_hostname = False
PROXY_SSL_CONTEXT.verify_mode = ssl.CERT_NONE # maybe we meet in the middle where we keep certificate verification on but we disable the hostname check? it will start finding proxies in the public lists. Ideally, you would leave on the certificate verification but disable the hostname verification. I'm using proxies where the server serves valid certificates so I can find valid ones. Workarounds I can think is retrying proxies that failed the proxy_ssl cert check to be done with verification off? |
@monosans any chance this could get added? I am maintaining my own version of your wonderful work but I think it is useful to more than just me ^-^ Just disabling the hostname check works which is nice. |
Changes: