[Twisted-Python] Issue with TLS failure modes

I'm having an issue properly handling TLS failure modes. For example consider the EchoServer and EchoClient code. If I use a TLS client with a TCP4 server, I do not get a handshake exception until I abort the connection. But I don't want to abort the connection unless I get a handshake error. What

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

>>You can't use connectSSL in combination with UNIX sockets I'm working on a rewrite of this system which will use endpoints once complete. So far I've got basic server and client endpoints running over TLS through our reverse proxy. Its working as expected on a given port, but I'd rather have t

Re: [Twisted-Python] Using twistd with -c option causes permission error

On Wed, 29 Aug 2018, at 11:04 PM, Jean-Paul Calderone wrote: > On Tue, Aug 28, 2018 at 5:54 AM Richard Shea > wrote:>> >> With Apache the process starts as root, reads the key and then makes >> the apache process run as a different, less powerful, user but I >> can't see how you can do the equiv

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

On Aug 30, 2018, at 1:22 PM, Sean DiZazzo wrote: > Can't seem to find a corresponding wraperServerTLS to the client function Tim > posted. There is no wrapServerTLS right now in Twisted itself. https://github.com/glyph/txsni/blob/master/txsni/tlsendpoint.py