-
Notifications
You must be signed in to change notification settings - Fork 296
SSL on ip-adresses: net::ERR_CERT_AUTHORITY_INVALID #287
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
Comments
How
If you need just encryption (protection against passive attacks, but not against active connection proxying), then In any case the proper way to use TLS in intranet would be using your own CA and adding its certificate where needed across the intranet. |
sorry for providing incomplete info, here's how it was generated:
|
This looks like a simple self-signed certificate. This:
looks suspicious. Browsers should not accept such certificates by default. Does it work from some other browser or from a fresh browser profile? Or what do you mean by "a websocket client"? |
apoligies, more info below:
shellscript is also testable by entering 'k' at https://xrsh.isvery.ninja/src/index.html |
Uh oh!
There was an error while loading. Please reload this page.
I can connect succesfully on my local machine (from webpage
https://localhost:8080/index.html
with a websocket client)However, when I load that same webpage on another device via its external ip (`https://192.168.0.44:8080/index.html), then the webbrowser fails and throws:
This seems no issue when using real domains, certificates, or reverse/websocket proxies.
However, just out of intranet curiosity: is there an easy way to get websocat encryption with IP-adresses?
The text was updated successfully, but these errors were encountered: