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

diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f
index 375d73bbc00d2859b80b1f98086f3c9bba5deba8..823f53634aa7d5390fabdf0718064852ece6892d 100644 (file)
--- 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