Document OMEMO for MUCs. Updates #1180
This commit is contained in:
parent
be1be3534c
commit
6f10f95d77
@ -6,6 +6,7 @@
|
|||||||
- UI: Always show the OMEMO lock icon (grayed out if not available).
|
- UI: Always show the OMEMO lock icon (grayed out if not available).
|
||||||
- Use `publish-options` with `pubsub#access_model` set to `open` when publishing OMEMO public keys and devices
|
- Use `publish-options` with `pubsub#access_model` set to `open` when publishing OMEMO public keys and devices
|
||||||
- Add a new `converse-pubsub` plugin, for generic PubSub operations
|
- Add a new `converse-pubsub` plugin, for generic PubSub operations
|
||||||
|
- #1180 It's now possible to use OMEMO in a MUC (if it's members-only and non-anonymous)
|
||||||
- #1353 Message Delivery Receipts not working because of the message "type" attribute
|
- #1353 Message Delivery Receipts not working because of the message "type" attribute
|
||||||
- #1374 Can't load embedded chat when changing `view_mode` between page reloads
|
- #1374 Can't load embedded chat when changing `view_mode` between page reloads
|
||||||
- #1376 Fixed some alignment issues in the sidebar
|
- #1376 Fixed some alignment issues in the sidebar
|
||||||
|
@ -44,7 +44,7 @@ If you've checked the "This is not a trusted device" checkbox when logging in,
|
|||||||
then `sessionStorage <https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage>`_
|
then `sessionStorage <https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage>`_
|
||||||
is used instead of localStorage and all data is cleared when you log out.
|
is used instead of localStorage and all data is cleared when you log out.
|
||||||
|
|
||||||
For this reason, OMEMO cannot be used when you've indicated that you're using
|
For this reason, OMEMO is disabled when you've indicated that you're using
|
||||||
an untrusted device. You would in any case not be able to decrypt previously
|
an untrusted device. You would in any case not be able to decrypt previously
|
||||||
received OMEMO messages, due to the Signal Protocol's forward secrecy and the
|
received OMEMO messages, due to the Signal Protocol's forward secrecy and the
|
||||||
fact that you don't have a pre-existing session.
|
fact that you don't have a pre-existing session.
|
||||||
@ -93,6 +93,16 @@ articles:
|
|||||||
* `What's wrong with webcrypto? <https://tonyarcieri.com/whats-wrong-with-webcrypto>`_
|
* `What's wrong with webcrypto? <https://tonyarcieri.com/whats-wrong-with-webcrypto>`_
|
||||||
* `Heartbleed and JavaScript crypto <https://tankredhase.com/2014/04/13/heartbleed-and-javascript-crypto/>`_
|
* `Heartbleed and JavaScript crypto <https://tankredhase.com/2014/04/13/heartbleed-and-javascript-crypto/>`_
|
||||||
|
|
||||||
|
OMEMO in Multi-user chats (MUC)
|
||||||
|
-------------------------------
|
||||||
|
|
||||||
|
Converse supports OMEMO encryption in groupchats, but only if the groupchat is
|
||||||
|
set to `members only` and `non-anonymous`. This is the same criteria used by
|
||||||
|
the popular Android XMPP client `Conversations <https://conversations.im/>`_.
|
||||||
|
|
||||||
|
If the groupchat is configured properly, you'll see the lock icon in the
|
||||||
|
toolbar.
|
||||||
|
|
||||||
|
|
||||||
Open chats via URL
|
Open chats via URL
|
||||||
==================
|
==================
|
||||||
|
Loading…
Reference in New Issue
Block a user