Mercurial > libervia-backend
view doc/jp/info.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 | ae09989e9feb |
children |
line wrap: on
line source
================================== info: retrieve various information ================================== ``info`` groups subcommands used to retrieve read-only informations. disco ===== Display discovery information (see `XEP-0030`_ for details). This can be used to check which features you server or a service is offering, and which items are available (items can be services like chat room, gateways, etc). You only have to specify the jid of the entity to check, and optionally a node. By default both infos and items are requested, but you can restrict what to request by using ``-t {infos,items,both}, --type {infos,items,both}`` .. _XEP-0030: https://xmpp.org/extensions/xep-0030.html example ------- Request infos and items from a server:: $ jp info disco example.org version ======= Request software version of an entity. You only need to specify the jid of the entity as positional argument. Depending of the software and its configuration, you have software version, software name, and the operating system on which the software is running. example ------- Check version of a server:: $ jp info version example.org session ------- Give information about the session of the given profile. You'll get the full jid currently used on the server, and the time when the session was started (which may not be the same time as when the connection with the XMPP server was started). example ------- Get session informations:: $ jp info session devices ------- List known devices for an entity. You'll get resource name, and data such as presence data, and identities (i.e. name and type of the client used). If entity's bare jid is not specified, a list of your own devices is returned. example ------- List known devices of Louise:: $ jp info devices louise@example.org Check if we have other devices connected:: $ jp info devices