diff options
| author | dec05eba <dec05eba@protonmail.com> | 2018-05-17 02:12:55 +0200 |
|---|---|---|
| committer | dec05eba <dec05eba@protonmail.com> | 2018-05-17 02:12:58 +0200 |
| commit | 528a61c86876de814ff4e65855926a750ba24587 (patch) | |
| tree | eb9e794211098965421e64e05baed2be142f43a6 /README.md | |
| parent | ba51ca6342454ab33b645d377405e36a9876ac5b (diff) | |
Avatars for everybody
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -14,5 +14,8 @@ The user that wants to join the channel using the invite key has to sign a messa If the creator of the invite key can verify that the message they received was signed with the public key that exists in the message and the message can be decrypted using the invite encryption key, then they will respond with the channel node encryption key. The user that created the invite key will then add the user to the channel and the user that wants to join will wait until they receive 'ADD DATA' node that with the public key that they requested to be added with, by receiving and decrypting node data with the key the got from the creator of the invite key. +# Handle incorrect decryption key +When joining a channel using invite key, we might be given an incorrect decryption key. If that is the case then currently the client crashes +because decryption fails. This should be gracefully handled # Screenshot  |