diff options
| author | metamuffin <metamuffin@disroot.org> | 2022-09-09 19:18:42 +0200 |
|---|---|---|
| committer | metamuffin <metamuffin@disroot.org> | 2022-09-09 19:18:42 +0200 |
| commit | 962ec1b9a0b44661e46acf81e867e81e87d53038 (patch) | |
| tree | 006ccc7d378dd193cffab581131f91e3235e7066 /readme.md | |
| parent | 7c0c2c0894796800da85514fc948b5662f1b7ab0 (diff) | |
| download | keks-meet-962ec1b9a0b44661e46acf81e867e81e87d53038.tar keks-meet-962ec1b9a0b44661e46acf81e867e81e87d53038.tar.bz2 keks-meet-962ec1b9a0b44661e46acf81e867e81e87d53038.tar.zst | |
watch-builder can be replace with `deno bundle --watch`
Diffstat (limited to 'readme.md')
| -rw-r--r-- | readme.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -22,7 +22,7 @@ GNU Affero General Public License version 3 only; See [COPYING](./COPYING). keks-meet _tries_ to be secure. However I am not a security expert. The current system works as follows: - 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 +- The server receives a salted SHA-256 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 |