make other_user_key optional for one flow of self-verification

pull/977/head
Hubert Chathi 5 years ago
parent fcfd5d99a1
commit 21ddf8507a

@ -141,8 +141,8 @@ In the second example, Dynabook scans Osborne2:
- Alice's user ID, - Alice's user ID,
- Osborne2's device key (optional), - Osborne2's device key (optional),
- what it thinks Dynabook's key is, as `other_device_key`, - what it thinks Dynabook's key is, as `other_device_key`,
- Alice's master key, both as `key_<key_id>` and `other_user_key` - Alice's master key as a `key_<key_id>` parameter and (optionally) a `other_user_key`
parameters, and parameter, and
- a random shared secret. - a random shared secret.
3. Dynabook scans the QR code shown by Osborne2. At this point, Dynabook knows 3. Dynabook scans the QR code shown by Osborne2. At this point, Dynabook knows
Alice's cross-signing key, and so it can trust it to sign other devices. It Alice's cross-signing key, and so it can trust it to sign other devices. It

Loading…
Cancel
Save