tyler.durden
/
openssh-portable
mirror of https://github.com/PowerShell/openssh-portable.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

upstream: chop some unnecessary and confusing verbiage from the 

security key protocol description; feedback from Ron Frederick

OpenBSD-Commit-ID: 048c9483027fbf9c995e5a51b3ac502989085a42
This commit is contained in:
djm@openbsd.org 2019-12-10 22:36:08 +00:00 committed by Damien Miller
parent 59175a350f
commit c4036fe75e
1 changed files with 3 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
PROTOCOL.u2f
View File

@ -150,15 +150,8 @@ SSH U2F signatures
------------------ ------------------
In addition to the message to be signed, the U2F signature operation In addition to the message to be signed, the U2F signature operation
requires a few additional parameters: requires the key handle and a few additional parameters. The signature
is signed over a blob that consists of:
byte control bits (e.g. "user presence required" flag)
byte[32] SHA256(message)
byte[32] SHA256(application)
byte key_handle length
byte[] key_handle
This signature is signed over a blob that consists of:
byte[32] SHA256(application) byte[32] SHA256(application)
byte flags (including "user present", extensions present) byte flags (including "user present", extensions present)
@ -170,7 +163,7 @@ The signature returned from U2F hardware takes the following format:
byte flags (including "user present") byte flags (including "user present")
uint32 counter uint32 counter
byte[32] ecdsa_signature (in X9.62 format). byte[] ecdsa_signature (in X9.62 format).
For use in the SSH protocol, we wish to avoid server-side parsing of ASN.1 For use in the SSH protocol, we wish to avoid server-side parsing of ASN.1
format data in the pre-authentication attack surface. Therefore, the format data in the pre-authentication attack surface. Therefore, the