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 Nov 6, 2023. It is now read-only.
it would be nice if I could give both server and client a static passphrase, with which the websocket traffic then is encrypted.
I know, you can use websockets with TLS and also the SSH traffic is encrypted already, but still, if a company intercepts TLS traffic and inspects it, you would see that SSH traffic is encapsulated.
The text was updated successfully, but these errors were encountered:
Hello,
it would be nice if I could give both server and client a static passphrase, with which the websocket traffic then is encrypted.
I know, you can use websockets with TLS and also the SSH traffic is encrypted already, but still, if a company intercepts TLS traffic and inspects it, you would see that SSH traffic is encapsulated.
The text was updated successfully, but these errors were encountered: