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
This commit is contained in:
parent
75f7f22a43
commit
22d4beb796
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue