diff options
author | metamuffin <metamuffin@disroot.org> | 2022-09-09 15:35:56 +0200 |
---|---|---|
committer | metamuffin <metamuffin@disroot.org> | 2022-09-09 15:35:56 +0200 |
commit | de8e2d40ed2744c4c25ec7cdbe778e1723dbb830 (patch) | |
tree | 11d7e40b6c74946f2c0a3fa6a416b729b2582146 /readme.md | |
parent | 8aaf7e201e58ec9ecb431a6ac05e07d0078b12b0 (diff) | |
download | keks-meet-de8e2d40ed2744c4c25ec7cdbe778e1723dbb830.tar keks-meet-de8e2d40ed2744c4c25ec7cdbe778e1723dbb830.tar.bz2 keks-meet-de8e2d40ed2744c4c25ec7cdbe778e1723dbb830.tar.zst |
refactor + identify
Diffstat (limited to 'readme.md')
-rw-r--r-- | readme.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -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 |