-
Notifications
You must be signed in to change notification settings - Fork 205
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
Self Signed SSL Cert with socketIO #54
Comments
+1 |
You are running a local socket.io server with a self-signed certificate and accessing the server from the same machine using localhost. Have you tried using verify=False without specifying the certificate?
|
Please feel free to reopen this issue if the suggestion above does not work. |
As an update, both server SSL certificate verification and client SSL certificate encryption seem to work properly in [email protected] with socketIO-client>=0.6.5.
http://docs.python-requests.org/en/master/user/advanced/#ssl-cert-verification |
λ python
|
can you help me out |
I'm having the same problem |
Hi.
I am trying to get socketio-client to connect to a local node.js server.
If I run straight http everything is fine.
If I attempt to access the server using https with Self Signed Certs I run into problems.
(I have a working python example connection to the server using urllib2 to post a JSON document so I am fairly sure it all works together.)
I want to use a self signed cert against node.js on my local machine (CN of the cert is the eventual domain)
If I specify a .pem file i.e.
verify='....../certs/server/server.pem'
with SocketIO('https://127.0.0.1:8443',
verify=verify,
cert=('certs/monitor/monitor.crt', 'certs/monitor/monitor.key')) as socketIO:
I get WARNING:socketIO_client:[waiting for connection] hostname '127.0.0.1' doesn't match u'
so its doing CN checking - can we disable this? I have started looking into the urllib3 connectionPooling code as there is an assert_hosts=False flag which should be applicable. However I cannot seem to make this work with socketIO.
If I use verify=False i.e.
SocketIO('https://127.0.0.1:8443',
verify=False,
cert=('certs/monitor/monitor.crt', 'certs/monitor/monitor.key')) as socketIO:
Then I get
WARNING:socketIO_client:[waiting for connection] [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
So it looks like verify is NOT being passed through successfully
in either case it seems to go into a loop attempting to access 127.0.0.1
Any help would be useful.
Excellent apart from that........
The text was updated successfully, but these errors were encountered: