commit edf52b6747680415025ce94602dc0c33dffdabfe
parent 4c98531aa7f0c18f42256de7c19fe89ebb4ec38a
Author: Remy Noulin <loader2x@gmail.com>
Date: Tue, 11 Jul 2023 10:37:07 +0200
update readme
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
@@ -29,5 +29,5 @@ I created `sel.c` to handle the various keys, there are functions that don't tak
The server keeps the same session keys and uses a bloom filter to detect when client are reusing session keys.
## `client4.c` and `server4.c`
-`server4.c` has the client public keys and if the client is valid when it connects.
-The clients can request the server public key, if the server public key is already know, it can send the first encrypted message directly.
+`server4.c` has the client public keys and if the client key is valid when it connects, it is authenticated.
+The clients can request the server public key, if the server public key is already known, it can send the first encrypted message directly.