Mercurial > libervia-backend
view doc/jp/identity.rst @ 3237:b0c57c9a4bd8
plugin XEP-0384: OMEMO trust policy:
OMEMO trust policy can now be specified. For now there are 2 policies:
- `manual`: each new device fingerprint must be explicitly trusted or not before the
device can be used, and the message sent
- `BTBV` (Blind Trust Before Verification): each new device fingerprint is automically
trusted, until user manually trust or not a device, in which case the behaviour becomes
the same as for `manual` for the entity. When using the Trust UI, user can put the
entity back to blind trust if they wish.
A message is send as feedback to user when a new device is/must be trusted, trying to
explain clearly what's happening to the user.
Devices which have been automically trusted are marked, so user can know which ones may
cause security issue.
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 27 Mar 2020 10:02:14 +0100 |
parents | 72583524cfd3 |
children | 6cf4bd6972c2 |
line wrap: on
line source
============================= identity: identity management ============================= Identity use several XMPP extensions (like vcards) to retrieve or set informations about an entity. For now it's really basic and only nickname and avatar are managed. get === Retrieve informations about the identity behind an XMPP entity. You only have to specify the jid of the entity, and you'll get (if set) his/her/its nickname and a link to the cached avatar. example -------- Get identity information about an entity:: $ jp identity get somebody@example.org set === Set identity data to the server, using various XMPP extensions. You set the data to change using ``-f KEY VALUE, --field KEY VALUE``, where ``KEY`` can only be ``nick`` at the moment. example ------- Set the nickname of default profile:: $ jp identity set -f nick toto