From 1fea3eadda1ba81e60ab388a1ddccf2d8d035bd0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Er=C3=A8be=20-=20Romain=20Gerard?= Date: Thu, 25 Aug 2016 13:49:26 +0200 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 16e4b97..d3abdc9 100644 --- a/README.md +++ b/README.md @@ -48,9 +48,9 @@ Start your wstunnel server with tls activated wstunnel --server wss://0.0.0.0:443 -r 127.0.0.1:22 ``` The server will listen on any interface on port 443 (https) and restrict traffic to be forwarded only to the ssh daemon. -Be aware that the server will use self signed certificate with weak cryptographic algorithm. +**Be aware that the server will use self signed certificate with weak cryptographic algorithm. It was made in order add the least possible overhead while still being compliant with tls. -So do not rely on wstunnel to protect your privacy, if you want to do forwards only traffic that is already secure by design (ex: https) +So do not rely on wstunnel to protect your privacy, if you want to do forwards only traffic that is already secure by design (ex: https)** Now on the client side start the client with ```