mirror of
https://github.com/chemhack/putty.git
synced 2025-07-22 18:26:18 +00:00
114 lines
4.8 KiB
HTML
114 lines
4.8 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
|
|
"http://www.w3.org/TR/html4/strict.dtd">
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=US-ASCII">
|
|
<title>SSH-2 names specified for PuTTY</title>
|
|
<link rel="previous" href="AppendixE.html">
|
|
<link rel="ToC" href="index.html">
|
|
<link rel="up" href="index.html">
|
|
<link rel="index" href="IndexPage.html">
|
|
<link rel="next" href="IndexPage.html">
|
|
</head>
|
|
<body>
|
|
<p><a href="AppendixE.html">Previous</a> | <a href="index.html">Contents</a> | <a href="IndexPage.html">Index</a> | <a href="IndexPage.html">Next</a></p>
|
|
|
|
<ul>
|
|
<li><a href="#sshnames">Appendix F: SSH-2 names specified for PuTTY</a>
|
|
<ul>
|
|
<li><a href="#sshnames-channel">F.1 Connection protocol channel request names</a></li>
|
|
<li><a href="#sshnames-kex">F.2 Key exchange method names</a></li>
|
|
<li><a href="#sshnames-encrypt">F.3 Encryption algorithm names</a></li>
|
|
</ul></li>
|
|
</ul>
|
|
<h1><a name="sshnames"></a><a name="AF"></a>Appendix F: SSH-2 names specified for PuTTY</h1>
|
|
<p>
|
|
There are various parts of the SSH-2 protocol where things are specified using a textual name. Names ending in <code>@putty.projects.tartarus.org</code> are reserved for allocation by the PuTTY team. Allocated names are documented here.
|
|
</p>
|
|
<h2><a name="sshnames-channel"></a><a name="SF.1"></a>F.1 Connection protocol channel request names</h2>
|
|
<p>
|
|
These names can be sent in a <code>SSH_MSG_CHANNEL_REQUEST</code> message.
|
|
</p>
|
|
<dl><dt>
|
|
<code>simple@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<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.
|
|
</dd>
|
|
<dt>
|
|
<code>winadj@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dd>
|
|
PuTTY sends this request along with some <code>SSH_MSG_CHANNEL_WINDOW_ADJUST</code> 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 <code>SSH_MSG_CHANNEL_FAILURE</code>.
|
|
</dd>
|
|
</dl>
|
|
<h2><a name="sshnames-kex"></a><a name="SF.2"></a>F.2 Key exchange method names</h2>
|
|
<dl><dt>
|
|
<code>rsa-sha1-draft-00@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa-sha256-draft-00@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa1024-sha1-draft-01@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa1024-sha256-draft-01@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa2048-sha256-draft-01@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa1024-sha1-draft-02@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa2048-sha512-draft-02@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa1024-sha1-draft-03@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa2048-sha256-draft-03@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa1024-sha1-draft-04@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>rsa2048-sha256-draft-04@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dd>
|
|
These appeared in various drafts of what eventually became RFC 4432. They have been superseded by <code>rsa1024-sha1</code> and <code>rsa2048-sha256</code>.
|
|
</dd>
|
|
</dl>
|
|
<h2><a name="sshnames-encrypt"></a><a name="SF.3"></a>F.3 Encryption algorithm names</h2>
|
|
<dl><dt>
|
|
<code>arcfour128-draft-00@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dt>
|
|
<code>arcfour256-draft-00@putty.projects.tartarus.org</code>
|
|
</dt>
|
|
<dd>
|
|
These were used in drafts of what eventually became RFC 4345. They have been superseded by <code>arcfour128</code> and <code>arcfour256</code>.
|
|
</dd>
|
|
</dl>
|
|
|
|
<hr><p>If you want to provide feedback on this manual or on the PuTTY tools themselves, see the <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html">Feedback page</a>.</p><address>
|
|
[$Id: blurb.but 9593 2012-07-29 13:38:31Z simon $]<br>
|
|
[$Id: intro.but 5593 2005-04-05 18:01:32Z jacob $]<br>
|
|
[$Id: gs.but 6815 2006-08-28 10:35:12Z simon $]<br>
|
|
[$Id: using.but 9149 2011-04-08 15:52:02Z jacob $]<br>
|
|
[$Id: config.but 9592 2012-07-28 19:30:12Z simon $]<br>
|
|
[$Id: pscp.but 9365 2011-12-10 12:07:46Z simon $]<br>
|
|
[$Id: psftp.but 8325 2008-11-24 18:19:55Z jacob $]<br>
|
|
[$Id: plink.but 9365 2011-12-10 12:07:46Z simon $]<br>
|
|
[$Id: pubkey.but 9422 2012-03-04 01:01:11Z jacob $]<br>
|
|
[$Id: pageant.but 6610 2006-03-14 11:21:59Z jacob $]<br>
|
|
[$Id: errors.but 9627 2012-08-26 09:50:57Z jacob $]<br>
|
|
[$Id: faq.but 9391 2012-01-30 00:29:32Z jacob $]<br>
|
|
[$Id: feedback.but 7824 2007-12-20 11:03:45Z simon $]<br>
|
|
[$Id: licence.but 9390 2012-01-26 18:53:53Z jacob $]<br>
|
|
[$Id: udp.but 5525 2005-03-19 02:29:57Z jacob $]<br>
|
|
[$Id: pgpkeys.but 5598 2005-04-05 19:36:25Z simon $]<br>
|
|
[$Id: index.but 9391 2012-01-30 00:29:32Z jacob $]</address></body>
|
|
</html>
|