]>
Commit | Line | Data |
---|---|---|
1c1af145 | 1 | \define{versionidsshnames} \versionid $Id$ |
2 | ||
3 | \A{sshnames} SSH-2 names specified for PuTTY | |
4 | ||
5 | There are various parts of the SSH-2 protocol where things are specified | |
6 | using a textual name. Names ending in \cw{@putty.projects.tartarus.org} | |
7 | are reserved for allocation by the PuTTY team. Allocated names are | |
8 | documented here. | |
9 | ||
10 | \H{sshnames-channel} Connection protocol channel request names | |
11 | ||
12 | These names can be sent in a \cw{SSH_MSG_CHANNEL_REQUEST} message. | |
13 | ||
14 | \dt \cw{simple@putty.projects.tartarus.org} | |
15 | ||
16 | \dd This is sent by a client to announce that it will not have more than | |
17 | one channel open at a time in the current connection (that one being | |
18 | the one the request is sent on). The intention is that the server, | |
19 | knowing this, can set the window on that one channel to something very | |
20 | large, and leave flow control to TCP. There is no message-specific data. | |
21 | ||
22 | \dt \cw{winadj@putty.projects.tartarus.org} | |
23 | ||
24 | \dd PuTTY sends this request along with some | |
25 | \cw{SSH_MSG_CHANNEL_WINDOW_ADJUST} messages as part of its window-size | |
26 | tuning. It can be sent on any type of channel. There is no | |
27 | message-specific data. Servers MUST treat it as an unrecognised request | |
28 | and respond with \cw{SSH_MSG_CHANNEL_FAILURE}. | |
29 | ||
30 | \H{sshnames-kex} Key exchange method names | |
31 | ||
32 | \dt \cw{rsa-sha1-draft-00@putty.projects.tartarus.org} | |
33 | ||
34 | \dt \cw{rsa-sha256-draft-00@putty.projects.tartarus.org} | |
35 | ||
36 | \dt \cw{rsa1024-sha1-draft-01@putty.projects.tartarus.org} | |
37 | ||
38 | \dt \cw{rsa1024-sha256-draft-01@putty.projects.tartarus.org} | |
39 | ||
40 | \dt \cw{rsa2048-sha256-draft-01@putty.projects.tartarus.org} | |
41 | ||
42 | \dt \cw{rsa1024-sha1-draft-02@putty.projects.tartarus.org} | |
43 | ||
44 | \dt \cw{rsa2048-sha512-draft-02@putty.projects.tartarus.org} | |
45 | ||
46 | \dt \cw{rsa1024-sha1-draft-03@putty.projects.tartarus.org} | |
47 | ||
48 | \dt \cw{rsa2048-sha256-draft-03@putty.projects.tartarus.org} | |
49 | ||
50 | \dt \cw{rsa1024-sha1-draft-04@putty.projects.tartarus.org} | |
51 | ||
52 | \dt \cw{rsa2048-sha256-draft-04@putty.projects.tartarus.org} | |
53 | ||
54 | \dd These appeared in various drafts of what eventually became RFC\_4432. | |
55 | They have been superseded by \cw{rsa1024-sha1} and \cw{rsa2048-sha256}. | |
56 | ||
57 | \H{sshnames-encrypt} Encryption algorithm names | |
58 | ||
59 | \dt \cw{arcfour128-draft-00@putty.projects.tartarus.org} | |
60 | ||
61 | \dt \cw{arcfour256-draft-00@putty.projects.tartarus.org} | |
62 | ||
63 | \dd These were used in drafts of what eventually became RFC\_4345. | |
64 | They have been superseded by \cw{arcfour128} and \cw{arcfour256}. |