|
|
@@ -167,18 +167,28 @@ bridge:
|
|
|
# Default to encryption, force-enable encryption in all portals the bridge creates
|
|
|
# This will cause the bridge bot to be in private chats for the encryption to work properly.
|
|
|
default: false
|
|
|
- # Options for automatic key sharing.
|
|
|
- key_sharing:
|
|
|
- # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
|
|
|
- # You must use a client that supports requesting keys from other users to use this feature.
|
|
|
- allow: false
|
|
|
- # Require the requesting device to have a valid cross-signing signature?
|
|
|
- # This doesn't require that the bridge has verified the device, only that the user has verified it.
|
|
|
- # Not yet implemented.
|
|
|
- require_cross_signing: false
|
|
|
- # Require devices to be verified by the bridge?
|
|
|
- # Verification by the bridge is not yet implemented.
|
|
|
- require_verification: true
|
|
|
+ # Require encryption, drop any unencrypted messages.
|
|
|
+ require: true
|
|
|
+ # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
|
|
|
+ # You must use a client that supports requesting keys from other users to use this feature.
|
|
|
+ allow_key_sharing: false
|
|
|
+ # What level of device verification should be required from users?
|
|
|
+ #
|
|
|
+ # Valid levels:
|
|
|
+ # unverified - Send keys to all device in the room.
|
|
|
+ # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
|
|
|
+ # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
|
|
|
+ # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
|
|
|
+ # Note that creating user signatures from the bridge bot is not currently possible.
|
|
|
+ # verified - Require manual per-device verification
|
|
|
+ # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
|
|
|
+ verification_levels:
|
|
|
+ # Minimum level for which the bridge should send keys to when bridging messages from Telegram to Matrix.
|
|
|
+ receive: unverified
|
|
|
+ # Minimum level that the bridge should accept for incoming Matrix messages.
|
|
|
+ send: unverified
|
|
|
+ # Minimum level that the bridge should require for accepting key requests.
|
|
|
+ share: cross-signed-tofu
|
|
|
# Options for Megolm room key rotation. These options allow you to
|
|
|
# configure the m.room.encryption event content. See:
|
|
|
# https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for
|
Tulir Asokan