Nihlaeth

I had the same problem in one of my projects, unfortunately I solved it using python 3 libraries, so this will be of limited use here. Nonetheless, maybe an example...

I'd love to port natlink as a whole to python 3, and for the python part that wouldn't pose a big problem. It's the c part that worries me there…...

https://docs.python.org/2/library/ssl.html Reading that, it shouldn't be too difficult. I'd be happy to make a pull request with the sockets wrapped in a TLS layer, and a script for creating certificates....

I haven't forgotten! With TLS, the server and client don't need each other's public keys ahead of time, the protocol takes care of the key exchange. Instead, the server and...

Awesome! I added a certificate creation script to the project, I wrote a little bit in the readme about how to use it. Now all that's left is actually wrapping...

Could you shed some light on the client socket situation? I'm looking at [line 81](https://github.com/dictation-toolbox/aenea/blob/add_ssl/client/aenea/communications.py#L81) because it looks like a promising place to wrap the socket, but as far as...

Note to self: make a version of [this class](https://github.com/dictation-toolbox/aenea/blob/add_ssl/client/aenea/communications.py#L40) that inherits from [SafeTransport](https://github.com/tcalmant/jsonrpclib/blob/master/jsonrpclib/jsonrpc.py#L458). I think that should enable SSL, though I still don't get what that socket from my previous...

Thanks for the explanation. No wrapping, but if I remember correctly, socket will throw an exception when attempting to connect to an SSL enabled socket unwrapped, so I'll have to...

On a different note, the need for hacks like this is exactly why I'm itching for asyncio. I've been looking at the natlink source, and I'm starting to believe that...

@mzizzi you're welcome :-) > Short of a natlink re-write I don't think that blocking io itself is the issue here. The aenea wants to know its execution context before...