Skip to content
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

Perhaps use socat instead of sni #27

Open
sakisf opened this issue Dec 14, 2013 · 1 comment
Open

Perhaps use socat instead of sni #27

sakisf opened this issue Dec 14, 2013 · 1 comment

Comments

@sakisf
Copy link

sakisf commented Dec 14, 2013

I am not sure if it would work, but perhaps you could use socat instead of sni with no verification (for these machines which do not take sni). You can route the incoming port (through dnsmasq or bind 9 or iptables) and have one instance running for each site you are looking to access.

i.e. socat TCP-LISTEN:810,reuseaddr,fork OPENSSL:www.netflix.com:443,verify=0
socat TCP-LISTEN:811,reuseaddr,fork OPENSSL:www.hulu.com:443,verify=0

Tried it directly from vps and works.

@themickman007
Copy link

I couldn't get this to work for me. Is it only forwarding www.netflix.com specifically or all subdomains eg signup.netflix.com.
Also I had trouble forwarding ports through iptables as each site needs to have it's ip entered individually which is a big job and prone to changing often. Bind was no help either as it forwards to other dns servers and I am not using dnsmasq in my configuration so I didn't test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants