summaryrefslogtreecommitdiff
path: root/PROTOCOL.u2f
diff options
context:
space:
mode:
authordjm@openbsd.org <djm@openbsd.org>2020-05-12 01:41:32 +0000
committerDamien Miller <djm@mindrot.org>2020-05-27 10:09:18 +1000
commit829451815ec207e14bd54ff5cf7e22046816f042 (patch)
treecd5ba444b647863c105b3669ad671c6b3e0375e1 /PROTOCOL.u2f
parent5a442cec92c0efd6fffb4af84bf99c70af248ef3 (diff)
upstream: fix non-ASCII quote that snuck in; spotted by Gabriel
Kihlman OpenBSD-Commit-ID: 04bcde311de2325d9e45730c744c8de079b49800
Diffstat (limited to 'PROTOCOL.u2f')
-rw-r--r--PROTOCOL.u2f2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f
index fd4325b3a..69347e999 100644
--- a/PROTOCOL.u2f
+++ b/PROTOCOL.u2f
@@ -40,7 +40,7 @@ primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2
40standard specifies additional key types, including one based on Ed25519. 40standard specifies additional key types, including one based on Ed25519.
41 41
42Use of U2F security keys does not automatically imply multi-factor 42Use of U2F security keys does not automatically imply multi-factor
43authentication. From sshds perspective, a security key constitutes a 43authentication. From sshd's perspective, a security key constitutes a
44single factor of authentication, even if protected by a PIN or biometric 44single factor of authentication, even if protected by a PIN or biometric
45authentication. To enable multi-factor authentication in ssh, please 45authentication. To enable multi-factor authentication in ssh, please
46refer to the AuthenticationMethods option in sshd_config(5). 46refer to the AuthenticationMethods option in sshd_config(5).