Le 23/07/2014 15:36, Alex Gaynor a écrit : > > That said, I've hit another issue, with SNI callbacks. The first argument to an > SNI callback is the socket. The callback is set up by some C code, which right > now has access to only the _socket.socket object, not the ssl.SSLSocket object, > which is what the public API needs there. > > Possible solutions are: > > * Pass the SSLObject *in addition* to the _socket.socket object to the C code. > This generates some additional divergence from the Python3 code, but is > probably basically straightforward. You mean for use with SSL_set_app_data?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4