RepoMirrors/openssh
1
0
Fork 0
mirror of git://anongit.mindrot.org/openssh.git synced 2024-12-22 10:00:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

upstream: some more corrections for documentation problems spotted

Browse Source 
by Ron Frederick

document certifiate private key format
correct flags type for sk-ssh-ed25519@openssh.com keys

OpenBSD-Commit-ID: fc4e9a1ed7f9f7f9dd83e2e2c59327912e933e74
This commit is contained in:
djm@openbsd.org 2019-12-10 23:37:31 +00:00 committed by Damien Miller
parent 22d4beb796
commit a62f4e1960
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
PROTOCOL.u2f
View File

@ -86,7 +86,7 @@ With a private half consisting of:
string "sk-ssh-ed25519@openssh.com"
string public key
string application (user-specified, but typically "ssh:")
uint32 flags
uint8 flags
string key_handle
string reserved
@ -110,6 +110,8 @@ information to the public key:
string signature key
string signature
and for security key ed25519 certificates:
string "sk-ssh-ed25519-cert-v01@openssh.com"
string nonce
string public key
@ -126,6 +128,15 @@ information to the public key:
string signature key
string signature
Both security key certificates use the following encoding for private keys:
string type (e.g. "sk-ssh-ed25519-cert-v01@openssh.com")
string pubkey (the above key/cert structure)
string application
uint8 flags
string key_handle
string reserved
During key generation, the hardware also returns attestation information
that may be used to cryptographically prove that a given key is
hardware-backed. Unfortunately, the protocol required for this proof is
@ -188,7 +199,6 @@ For Ed25519 keys the signature is encoded as:
byte flags
uint32 counter
ssh-agent protocol extensions
-----------------------------