Daphne should use Twisted's strports/serverFromString for TLS/ACME support

This would replace this code (https://github.com/andrewgodwin/daphne/blob/master/daphne/server.py#L46) with a user passing a strports description on the command line, which is fed into http://twistedmatrix.com/documents/current/api/twisted.internet.endpoints.html#serverFromString. For example, to support unix sockets it would be unix:/var/run/finger, for TCP it’d be tcp:8000, for basic TLS it would be ssl:443:privateKey=key.pem:certKey=crt.pem, for txsni (TLS w/ SNI) it would be txsni:certificates:tcp:443, and for the automatic, turn-on TLS+SNI, it would be le:/srv/www/certs:tcp:443 (https://github.com/mithrandi/txacme).

I’m happy to implement this, but I thought I’d file an issue since it’s been on my mind for so long 😃

[andrewgodwin]

It does, you have to just use Twisted endpoint syntax and pass it to Daphne using the -e switch. For example:

daphne -e ssl:port=443:privateKey=/etc/ssl/server.pem:extraCertChain=/etc/ssl/chain.pem:sslmethod=SSLv3_METHOD:dhParameters=dh_param_1024.pem

More docs on this here: https://twistedmatrix.com/documents/16.4.1/core/howto/endpoints.html#servers - though there are other things you can do with Twisted endpoints that aren’t there, like let’s encrypt support.

[davidmarquis]

Also explained pretty clearly on the Daphne README: https://github.com/django/daphne (look for “SSL” on the page)