From 21ddf8507aae22dbf61311de2d20c95cec1dcfbd Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Wed, 29 Jan 2020 17:52:18 -0500 Subject: [PATCH] make other_user_key optional for one flow of self-verification --- proposals/1543-qr_code_key_verification.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1543-qr_code_key_verification.md b/proposals/1543-qr_code_key_verification.md index 392ef028..c2e2d9d4 100644 --- a/proposals/1543-qr_code_key_verification.md +++ b/proposals/1543-qr_code_key_verification.md @@ -141,8 +141,8 @@ In the second example, Dynabook scans Osborne2: - Alice's user ID, - Osborne2's device key (optional), - what it thinks Dynabook's key is, as `other_device_key`, - - Alice's master key, both as `key_` and `other_user_key` - parameters, and + - Alice's master key as a `key_` parameter and (optionally) a `other_user_key` + parameter, and - a random shared secret. 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