upstream: use consistent field names (s/char/byte)
in format description OpenBSD-Commit-ID: 3de33572733ee7fcfd7db33d37db23d2280254f0
This commit is contained in:
parent
32e82a392d
commit
7ec81daad0
12
PROTOCOL.key
12
PROTOCOL.key
|
@ -11,7 +11,7 @@ an encrypted list of matching private keys.
|
|||
string ciphername
|
||||
string kdfname
|
||||
string kdfoptions
|
||||
int number of keys N
|
||||
uint32 number of keys N
|
||||
string publickey1
|
||||
string publickey2
|
||||
...
|
||||
|
@ -42,11 +42,11 @@ of the cipher block size.
|
|||
...
|
||||
string privatekeyN
|
||||
string commentN
|
||||
char 1
|
||||
char 2
|
||||
char 3
|
||||
byte 1
|
||||
byte 2
|
||||
byte 3
|
||||
...
|
||||
char padlen % 255
|
||||
byte padlen % 255
|
||||
|
||||
where each private key is encoded using the same rules as used for
|
||||
SSH agent.
|
||||
|
@ -68,4 +68,4 @@ For unencrypted keys the cipher "none" and the KDF "none"
|
|||
are used with empty passphrases. The options if the KDF "none"
|
||||
are the empty string.
|
||||
|
||||
$OpenBSD: PROTOCOL.key,v 1.2 2021/05/07 02:29:40 djm Exp $
|
||||
$OpenBSD: PROTOCOL.key,v 1.3 2022/07/01 04:45:50 djm Exp $
|
||||
|
|
Loading…
Reference in New Issue