Skip to content

bad certificate alerts with accept_ssl() #32

Description

@von

For some reason, the client is croaking on some certificate I generate.

And I need to handle this error properly (getting a better message might help understand the certificate problem).

2011-07-05 19:21:03,792:Thread-70:ERROR:Uncaught exception responding to 127.0.0.1
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 582, in process_request_thread
self.finish_request(request, client_address)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 323, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 639, in init
self.handle()
File "/Users/von/develop/PerProxy/ProxyServer.py", line 83, in handle
self.start_ssl(key_file, cert_file)
File "/Users/von/develop/PerProxy/ProxyServer.py", line 175, in start_ssl
ssl_sock.accept_ssl()
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/M2Crypto-0.20.2-py2.7-macosx-10.3-fat.egg/M2Crypto/SSL/Connection.py", line 150, in accept_ssl
return m2.ssl_accept(self.ssl)
SSLError: sslv3 alert bad certificate

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions