From 7ec81daad0e03a64e8d91c5590960c48c1a899a3 Mon Sep 17 00:00:00 2001 From: "djm@openbsd.org" Date: Fri, 1 Jul 2022 04:45:50 +0000 Subject: upstream: use consistent field names (s/char/byte) in format description OpenBSD-Commit-ID: 3de33572733ee7fcfd7db33d37db23d2280254f0 --- PROTOCOL.key | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'PROTOCOL.key') diff --git a/PROTOCOL.key b/PROTOCOL.key index 38df268b..cbf7a702 100644 --- a/PROTOCOL.key +++ b/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 $ -- cgit v1.2.1