diff options
| author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2023-11-14 17:25:09 +0000 |
|---|---|---|
| committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2023-11-14 17:25:09 +0000 |
| commit | 89aa5c08f94dadf1cb80ac9b6e8b49caf5df3c5c (patch) | |
| tree | b8fb5accb8d5560edfc8e0844d3a5349fa37d1a8 /spec/ssh-protocols.md | |
| parent | 16010a5890741032c0501e4e33209aa37aeccfea (diff) | |
| download | torspec-89aa5c08f94dadf1cb80ac9b6e8b49caf5df3c5c.tar.gz torspec-89aa5c08f94dadf1cb80ac9b6e8b49caf5df3c5c.zip | |
ssh-protocols.md: Explain what PROTOCOL.md means
Diffstat (limited to 'spec/ssh-protocols.md')
| -rw-r--r-- | spec/ssh-protocols.md | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/spec/ssh-protocols.md b/spec/ssh-protocols.md index 990bb02..49c58d2 100644 --- a/spec/ssh-protocols.md +++ b/spec/ssh-protocols.md @@ -76,10 +76,23 @@ In each case we specify/reference * the name of the "public key algorithm" (RFC4250 4.11.3), * the underlying cryptographic algorithm(s), * the public key data - ("key/certificate data" in RFC4716 3.4) + ("key/certificate data" in + [RFC4253 6.6](https://datatracker.ietf.org/doc/html/rfc4253#section-6.6)) * the private key data (`privatekey1`, `privatekey2`, `privatekeyN` in `PROTOCOL.key`) +### Encoding of the public key data + +OpenSSH `PROTOCOL.key` does not clearly state +the contents of the `publickey1`/`publickey2`/`publickeyN` fields +in the outer (unencrypted) section (`PROTOCOL.key` s1), +so we state it here. + +Each `publickey` consists of the encoded public key +as per +[RFC4253 6.6](https://datatracker.ietf.org/doc/html/rfc4253#section-6.6) +(under "Certificates and public keys are encoded as follows"). + ### `x25519@spec.torproject.org` These refer to keys for |