From de8e2d40ed2744c4c25ec7cdbe778e1723dbb830 Mon Sep 17 00:00:00 2001 From: metamuffin Date: Fri, 9 Sep 2022 15:35:56 +0200 Subject: refactor + identify --- readme.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'readme.md') diff --git a/readme.md b/readme.md index c3ae098..bbab7d4 100644 --- a/readme.md +++ b/readme.md @@ -11,6 +11,7 @@ a web conferencing application - Screen capture - Multiple streams - Noise suppression (rnnoise) +- End-to-end-encryption ## Todo-List @@ -23,6 +24,7 @@ a web conferencing application - Test some options like `camera_facing_mode` - Signing key for each user - Built-in storage for known keys +- Prevent a client from sendin differing user names to other clients ## Security @@ -31,7 +33,6 @@ keks-meet _tries_ to be secure. However I am not a security expert. The current - The room name is set in the section of the URL (-> not sent to the server) - The server receives a salted hash of the room name to group client of a room - We use PBKDF2 (constant salt; 250000 iterations) to derive a 256-bit AES-GCM key -- - All relayed message contents are encrypted with this key. - Message recipient is visible to the server - The server assigns user ids -- cgit v1.2.3-70-g09d2