diff options
| author | dtucker@openbsd.org <dtucker@openbsd.org> | 2020-02-21 00:04:43 +0000 |
|---|---|---|
| committer | Darren Tucker <dtucker@dtucker.net> | 2020-02-21 12:27:23 +1100 |
| commit | 0001576a096f788d40c2c0a39121cff51bf961ad (patch) | |
| tree | cb99b996fcc37796af913bcdded8811f6bf48b9d /PROTOCOL.u2f | |
| parent | 99ff8fefe4b2763a53778d06b5f74443c8701615 (diff) | |
upstream: Fix some typos and an incorrect word in docs. Patch from
itoama at live.jp via github PR#172.
OpenBSD-Commit-ID: 166ee8f93a7201fef431b9001725ab8b269d5874
Diffstat (limited to 'PROTOCOL.u2f')
| -rw-r--r-- | PROTOCOL.u2f | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f index 748111d5..45995870 100644 --- a/PROTOCOL.u2f +++ b/PROTOCOL.u2f @@ -142,7 +142,7 @@ choose not to include this information in the public key or save it by default. Attestation information is useful for out-of-band key and certificate -registration worksflows, e.g. proving to a CA that a key is backed +registration workflows, e.g. proving to a CA that a key is backed by trusted hardware before it will issue a certificate. To support this case, OpenSSH optionally allows retaining the attestation information at the time of key generation. It will take the following format: @@ -169,7 +169,7 @@ is signed over a blob that consists of: byte[] extensions byte[32] SHA256(message) -No extensons are yet defined for SSH use. If any are defined in the future, +No extensions are yet defined for SSH use. If any are defined in the future, it will be possible to infer their presence from the contents of the "flags" value. |