From 363c8357e8de4a2478547f1ccbdf9a7038101cec Mon Sep 17 00:00:00 2001 From: Tom Smeding Date: Fri, 11 Sep 2020 15:15:20 +0200 Subject: Update readme to reflect current reality a bit better --- README.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index d41d4bc..f6c7a5b 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,15 @@ # tomsg tomsg is a simple chat server with a couple of clients: a webpage, a -[weechat](https://weechat.org/) plugin and an Android app. Its main interface -is over a TCP socket, but there is a websocket bridge to support web access. -There is basically no security. The storage backend is an SQLite database. +[weechat](https://weechat.org/) plugin and an Android app. The client-server +protocol is documented in `protocol.md`. -The client-server protocol is documented in `protocol.md`; however, for -security, clients should always connect through either the SSH proxy or the -websocket proxy behind an SSL terminator. +The server accepts connections over a simple TCP socket, but for actual use you +should, of course, encrypt that connection. This can be done in any way you +please, but the supported options are using the websocket proxy behind a TLS +terminator or using the SSH proxy on the client and server sides. This SSH +proxy only uses the SSH protocol for its encryption; authentication is still +done as in the normal tomsg protocol. + +The server storage backend is an SQLite database; the goal is that it is +lightweight and fast. -- cgit v1.2.3-70-g09d2