Indeed, in Twisted, the SSL.Connection is constructed with a memory BIO. And in
fact there may not be a socket in the loop at all!
What are you trying to do with `getpeername()`? Hopefully there's a similar
Twisted API that you could work with.
-glyph
> On Sep 5, 2019, at 11:07 PM, Sean DiZaz
Perhaps this line from OpenSSL.SSL.Connection is a clue.
"socket may be None; in this case, the Connection is created with a memory
BIO: see the bio_read(), bio_write(), and bio_shutdown() methods."
https://www.pyopenssl.org/en/stable/api/ssl.html#OpenSSL.SSL.Connection
On Wed, Sep 4, 2019 at 1:3
Hi,
I noticed that PyOpenSSL SNI callbacks (set with
*ctx.set_tlsext_servername_callback*) receive a *OpenSSL.SSL.Connection*
object within Twisted that have an empty *_socket* property, while this
property *is* actually set when using *PyOpenSSL* directly. For my use-case
this is a problem as I w
