-
Notifications
You must be signed in to change notification settings - Fork 88
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
Use this as a proxy to old SSL/TLS server? #50
Comments
Can you run the web management console without those self signed certs on a non-public localhost port and use ssl-proxy on the same machine to add SSL for incoming requests? |
The web console is contained to the unit on the local network. It supports SSLv3 and TLS 1.0 I don't have a way of running it on the same machine. ssl-proxy is running on my laptop on the same network. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a Wyse thin client running a web management console on https 443
Nothing in the modern age will talk to it as it's using a very old SSL/TLS self-signed cert from 2011.
I tried using ssl-proxy to connect but still run into issues with the old ciphers not being accepted. Is there any way to do this?
The text was updated successfully, but these errors were encountered: