You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2019. It is now read-only.
Thank you for https, but the game server (the one using port 25921) is still unencrypted. Though it seems to be unneeded because if you play using special app privacy risks (keystroke biometrics) are mitigated by sending info at once and thus destroying such kind of info.
The text was updated successfully, but these errors were encountered:
I know the EFF would disagree, but I don't see the point in using TLS everywhere. I there is no crucial or important information sent (besides, theoretically the keystrokes, but what would you plan on doing with a half solved regular expression?) since the protocol is well specified.
I'm going to leave this open for debate, but for the sake of simplicity, I wouldn't put any manpower into adding TLS for now.
Thank you for https, but the game server (the one using port 25921) is still unencrypted. Though it seems to be unneeded because if you play using special app privacy risks (keystroke biometrics) are mitigated by sending info at once and thus destroying such kind of info.
The text was updated successfully, but these errors were encountered: