would be nice if some people could test it before i release it! :)
To test in springlobby: server->disconnect, server->connect, select TLS... done

requires at least this commit: https://github.com/springlobby/springlo ... 83ab0ffe7d
Implementation details
For the connection openssl is used and only the certificate fingerprint is checked. Thats basicly the same es certificate-pinning.
This check is hardcoded atm, this should be changed soon.
The win32 development build has already tls-support, too.
when tls is used in springlobby.log (currently) this shows up:
Message /home/abma/dev/SpringLobby/src/socket.cpp:282 Certificate fingerprint: 0124dc0f4295b401a2d81ade3dc81b7a467eb9a70b0a4912b5e15fede735fe73
Message /home/abma/dev/SpringLobby/src/socket.cpp:286 Using TLSv1.2
Message /home/abma/dev/SpringLobby/src/socket.cpp:289 Using cipher ECDHE-RSA-AES256-GCM-SHA384
for details see https://github.com/springlobby/springlo ... socket.cpp
STARTTLS example client
This simple client written in python initates the tls connection (but does nothing else):
https://github.com/spring/uberserver/bl ... sclient.py
Note: this is my first tls-server (=uberserver) and client (=SpringLobby), so hopefully i didn't introduce some horrible security hole like others did. Hints are welcome!
