Antoine Pitrou antoine at python.org
Wed Jul 23 23:02:26 CEST 2014

• Previous message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
• Next message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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?

---

• Previous message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
• Next message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list