summaryrefslogtreecommitdiffstats
path: root/PROTOCOL.u2f
diff options
context:
space:
mode:
authordjm@openbsd.org <djm@openbsd.org>2019-12-10 23:21:56 +0000
committerDamien Miller <djm@mindrot.org>2019-12-11 19:11:07 +1100
commit22d4beb79622fc82d7111ac941269861fc7aef8d (patch)
tree70f7aeea448c02c9d0cafb37584778829f3bf4af /PROTOCOL.u2f
parent75f7f22a43799f6d25dffd9d6683de1601da05a3 (diff)
upstream: loading security keys into ssh-agent used the extension
constraint "sk-provider@openssh.com", not "sk@openssh.com"; spotted by Ron Frederick OpenBSD-Commit-ID: dbfba09edbe023abadd5f59c1492df9073b0e51d
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 375d73bb..823f5363 100644
--- a/PROTOCOL.u2f
+++ b/PROTOCOL.u2f
@@ -205,7 +205,7 @@ with a new key constraint extension to encode a path to the middleware
library for the key. The format of this constraint extension would be:
byte SSH_AGENT_CONSTRAIN_EXTENSION
- string sk@openssh.com
+ string sk-provider@openssh.com
string middleware path
This constraint-based approach does not present any compatibility