summaryrefslogtreecommitdiff
path: root/usr.bin
diff options
context:
space:
mode:
authorDamien Miller <djm@cvs.openbsd.org>2019-12-10 23:21:57 +0000
committerDamien Miller <djm@cvs.openbsd.org>2019-12-10 23:21:57 +0000
commit3b2b47a49dcb789a3b1f5c71e5e252b581d339d5 (patch)
tree0a5245995b1391d251b8ff9709f07fc82155a600 /usr.bin
parent81cf4ad0d3392f4378860219aac1a2a6377e81c5 (diff)
loading security keys into ssh-agent used the extension constraint
"sk-provider@openssh.com", not "sk@openssh.com"; spotted by Ron Frederick
Diffstat (limited to 'usr.bin')
-rw-r--r--usr.bin/ssh/PROTOCOL.u2f2
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.bin/ssh/PROTOCOL.u2f b/usr.bin/ssh/PROTOCOL.u2f
index 375d73bbc00..823f53634aa 100644
--- a/usr.bin/ssh/PROTOCOL.u2f
+++ b/usr.bin/ssh/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