mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-25 01:02:24 +00:00
4d8782e74f
I've shifted away from using the SVN revision number as a monotonic version identifier (replacing it in the Windows version resource with a count of days since an arbitrary epoch), and I've removed all uses of SVN keyword expansion (replacing them with version information written out by Buildscr). While I'm at it, I've done a major rewrite of the affected code which centralises all the computation of the assorted version numbers and strings into Buildscr, so that they're all more or less alongside each other rather than scattered across multiple source files. I've also retired the MD5-based manifest file system. A long time ago, it seemed like a good idea to arrange that binaries of PuTTY would automatically cease to identify themselves as a particular upstream version number if any changes were made to the source code, so that if someone made a local tweak and distributed the result then I wouldn't get blamed for the results. Since then I've decided the whole idea is more trouble than it's worth, so now distribution tarballs will have version information baked in and people can just cope with that. [originally from svn r10262]
63 lines
2.3 KiB
Plaintext
63 lines
2.3 KiB
Plaintext
\A{sshnames} SSH-2 names specified for PuTTY
|
|
|
|
There are various parts of the SSH-2 protocol where things are specified
|
|
using a textual name. Names ending in \cw{@putty.projects.tartarus.org}
|
|
are reserved for allocation by the PuTTY team. Allocated names are
|
|
documented here.
|
|
|
|
\H{sshnames-channel} Connection protocol channel request names
|
|
|
|
These names can be sent in a \cw{SSH_MSG_CHANNEL_REQUEST} message.
|
|
|
|
\dt \cw{simple@putty.projects.tartarus.org}
|
|
|
|
\dd This is sent by a client to announce that it will not have more than
|
|
one channel open at a time in the current connection (that one being
|
|
the one the request is sent on). The intention is that the server,
|
|
knowing this, can set the window on that one channel to something very
|
|
large, and leave flow control to TCP. There is no message-specific data.
|
|
|
|
\dt \cw{winadj@putty.projects.tartarus.org}
|
|
|
|
\dd PuTTY sends this request along with some
|
|
\cw{SSH_MSG_CHANNEL_WINDOW_ADJUST} messages as part of its window-size
|
|
tuning. It can be sent on any type of channel. There is no
|
|
message-specific data. Servers MUST treat it as an unrecognised request
|
|
and respond with \cw{SSH_MSG_CHANNEL_FAILURE}.
|
|
|
|
\H{sshnames-kex} Key exchange method names
|
|
|
|
\dt \cw{rsa-sha1-draft-00@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa-sha256-draft-00@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa1024-sha1-draft-01@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa1024-sha256-draft-01@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa2048-sha256-draft-01@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa1024-sha1-draft-02@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa2048-sha512-draft-02@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa1024-sha1-draft-03@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa2048-sha256-draft-03@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa1024-sha1-draft-04@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{rsa2048-sha256-draft-04@putty.projects.tartarus.org}
|
|
|
|
\dd These appeared in various drafts of what eventually became RFC\_4432.
|
|
They have been superseded by \cw{rsa1024-sha1} and \cw{rsa2048-sha256}.
|
|
|
|
\H{sshnames-encrypt} Encryption algorithm names
|
|
|
|
\dt \cw{arcfour128-draft-00@putty.projects.tartarus.org}
|
|
|
|
\dt \cw{arcfour256-draft-00@putty.projects.tartarus.org}
|
|
|
|
\dd These were used in drafts of what eventually became RFC\_4345.
|
|
They have been superseded by \cw{arcfour128} and \cw{arcfour256}.
|