doc (encryption, cli): document Pubsub Targeted Encryption:
a small section has been added to `encryption` to explain the difference with OXPS, and the `--encrypt-for` arguments are explained. fix 382
This commit is contained in:
parent
e735ae6a58
commit
dd434fbf1f
1 changed files with 33 additions and 1 deletions
|
|
@ -92,6 +92,26 @@ To handle encrypted pubsub node shared secrets from command line, you may use
|
|||
|
||||
.. _OpenPGP: https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP
|
||||
|
||||
Pubsub Targeted Encryption
|
||||
==========================
|
||||
|
||||
It is also possible to encrypt a single pubsub item for a restricted set of users. This is
|
||||
different from the pubsub encryption explained above, as if you want to encrypt for a
|
||||
different set of users, you need to re-encrypt all concerned items, so this is more
|
||||
adapted for use cases when you only want to encrypt a few items in a pubsub node.
|
||||
|
||||
On the other hand, you have all the properties of the algorithm used (for now, only OMEMO
|
||||
2 is supported), which means that you can have `Perfect Forward Secrecy`_ for algorithms
|
||||
supporting it (it's the case for OMEMO.)
|
||||
|
||||
.. note::
|
||||
|
||||
Pubsub Targeted Encryption(PTE) specification is not currently an official XEP (XMPP
|
||||
Extension Protocol), it is about to be examinated by "XMPP council". This documentation
|
||||
will be updated with the evolution of the situation.
|
||||
|
||||
.. _Perfect Forward Secrecy: https://en.wikipedia.org/wiki/Forward_secrecy
|
||||
|
||||
Pubsub Signature
|
||||
================
|
||||
|
||||
|
|
@ -124,4 +144,3 @@ To handle pubsub signatures from command line, you may use
|
|||
.. _"publisher" attribute: https://xmpp.org/extensions/xep-0060.html#publisher-publish-success-publisher
|
||||
|
||||
.. _Pubsub Signing protoXEP: https://github.com/xsf/xeps/pull/1228
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue