diff options
Diffstat (limited to 'doc/pubkeyfmt.but')
| -rw-r--r-- | doc/pubkeyfmt.but | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/pubkeyfmt.but b/doc/pubkeyfmt.but index 78da4885..836ed527 100644 --- a/doc/pubkeyfmt.but +++ b/doc/pubkeyfmt.but @@ -7,7 +7,7 @@ In this appendix, binary data structures are described using data type representations such as \cq{uint32}, \cq{string} and \cq{mpint} as used in the SSH protocol standards themselves. These are defined authoritatively by -\W{https://tools.ietf.org/html/rfc4251#section-5}{RFC 4251 section 5}, +\W{https://www.rfc-editor.org/rfc/rfc4251#section-5}{RFC 4251 section 5}, \q{Data Type Representations Used in the SSH Protocols}. \H{ppk-overview} Overview @@ -86,7 +86,7 @@ can contain any byte values other than 13 and 10 (CR and LF). The next part of the file gives the public key. This is stored unencrypted but base64-encoded -(\W{https://tools.ietf.org/html/rfc4648}{RFC 4648}), and is preceded +(\W{https://www.rfc-editor.org/rfc/rfc4648}{RFC 4648}), and is preceded by a header line saying how many lines of base64 data are shown, looking like this: @@ -241,7 +241,7 @@ of \e{y} in the group generated by \e{g} mod \e{p}. \S{ppk-privkey-ecdsa} NIST elliptic-curve keys -NIST elliptic-curve keys are stored using one of the following +\i{NIST} elliptic-curve keys are stored using one of the following \s{algorithm-name} values, each corresponding to a different elliptic curve and key size: |