nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
Code Issues Projects Releases Wiki Activity

Standardise RFC URLs in docs and comments.

Browse Source 
(Plus one internet-draft URL.)
This commit is contained in:
Jacob Nevins 2022-09-11 23:59:12 +01:00
parent 3f3f1987aa
commit 5fdfe5ac83
6 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
crypto/ecc-ssh.c
View File

@ -6,7 +6,7 @@
* References: * References:
* *
* Elliptic curves in SSH are specified in RFC 5656: * Elliptic curves in SSH are specified in RFC 5656:
* http://tools.ietf.org/html/rfc5656 * https://www.rfc-editor.org/rfc/rfc5656
* *
* That specification delegates details of public key formatting and a * That specification delegates details of public key formatting and a
* lot of underlying mechanism to SEC 1: * lot of underlying mechanism to SEC 1:

6
doc/authplugin.but
View File

@ -500,14 +500,14 @@ cases) after \cw{PLUGIN_PROTOCOL_ACCEPT}
\H{authplugin-refs} References \H{authplugin-refs} References
\B{authplugin-ref-arch} \W{https://datatracker.ietf.org/doc/html/rfc4251}{RFC 4251}, \q{The Secure Shell (SSH) Protocol \B{authplugin-ref-arch} \W{https://www.rfc-editor.org/rfc/rfc4251}{RFC 4251}, \q{The Secure Shell (SSH) Protocol
Architecture}. Architecture}.
\B{authplugin-ref-userauth} \W{https://datatracker.ietf.org/doc/html/rfc4252}{RFC \B{authplugin-ref-userauth} \W{https://www.rfc-editor.org/rfc/rfc4252}{RFC
4252}, \q{The Secure Shell (SSH) Authentication Protocol}. 4252}, \q{The Secure Shell (SSH) Authentication Protocol}.
\B{authplugin-ref-ki} \B{authplugin-ref-ki}
\W{https://datatracker.ietf.org/doc/html/rfc4256}{RFC 4256}, \W{https://www.rfc-editor.org/rfc/rfc4256}{RFC 4256},
\q{Generic Message Exchange Authentication for the Secure Shell \q{Generic Message Exchange Authentication for the Secure Shell
Protocol (SSH)} (better known by its wire id Protocol (SSH)} (better known by its wire id
\q{keyboard-interactive}). \q{keyboard-interactive}).

2
doc/config.but
View File

@ -1950,7 +1950,7 @@ connection.
\b Selecting \I{HTTP proxy}\q{HTTP CONNECT} allows you to proxy your \b Selecting \I{HTTP proxy}\q{HTTP CONNECT} allows you to proxy your
connections through a web server supporting the HTTP \cw{CONNECT} command, connections through a web server supporting the HTTP \cw{CONNECT} command,
as documented in \W{http://www.ietf.org/rfc/rfc2817.txt}{RFC 2817}. as documented in \W{https://www.rfc-editor.org/rfc/rfc2817}{RFC 2817}.
\b Selecting \q{SOCKS 4} or \q{SOCKS 5} allows you to proxy your \b Selecting \q{SOCKS 4} or \q{SOCKS 5} allows you to proxy your
connections through a \i{SOCKS server}. connections through a \i{SOCKS server}.

4
doc/pubkeyfmt.but
View File

@ -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 representations such as \cq{uint32}, \cq{string} and \cq{mpint} as
used in the SSH protocol standards themselves. These are defined used in the SSH protocol standards themselves. These are defined
authoritatively by 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}. \q{Data Type Representations Used in the SSH Protocols}.
\H{ppk-overview} Overview \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 The next part of the file gives the public key. This is stored
unencrypted but base64-encoded 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, by a header line saying how many lines of base64 data are shown,
looking like this: looking like this:

2
doc/sshnames.but
View File

@ -70,7 +70,7 @@ They have been superseded by \cw{arcfour128} and \cw{arcfour256}.
The SSH agent protocol, which is only specified in an Internet-Draft The SSH agent protocol, which is only specified in an Internet-Draft
at the time of writing at the time of writing
(\W{https://tools.ietf.org/html/draft-miller-ssh-agent}\cw{draft-miller-ssh-agent}), (\W{https://datatracker.ietf.org/doc/html/draft-miller-ssh-agent}\cw{draft-miller-ssh-agent}),
defines an extension mechanism. These names can be sent in an defines an extension mechanism. These names can be sent in an
\cw{SSH_AGENTC_EXTENSION} message. \cw{SSH_AGENTC_EXTENSION} message.

2
ssh/kex2-client.c
View File

@ -721,7 +721,7 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted)
* If this the first KEX, save the GSS context for "gssapi-keyex" * If this the first KEX, save the GSS context for "gssapi-keyex"
* authentication. * authentication.
* *
* http://tools.ietf.org/html/rfc4462#section-4 * https://www.rfc-editor.org/rfc/rfc4462#section-4
* *
* This method may be used only if the initial key exchange was * This method may be used only if the initial key exchange was
* performed using a GSS-API-based key exchange method defined in * performed using a GSS-API-based key exchange method defined in