1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Network Working Group B. Harris
Request for Comments: 4345 January 2006
Category: Standards Track
<span class="h1">Improved Arcfour Modes for</span>
<span class="h1">the Secure Shell (SSH) Transport Layer Protocol</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document specifies methods of using the Arcfour cipher in the
Secure Shell (SSH) protocol that mitigate the weakness of the
cipher's key-scheduling algorithm.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Secure Shell (SSH) [<a href="./rfc4251" title=""The Secure Shell (SSH) Protocol Architecture"">RFC4251</a>] is a secure remote-login protocol. It
allows for the use of an extensible variety of symmetric cipher
algorithms to provide confidentiality for data in transit. One of
the algorithms specified in the base protocol is "arcfour", which
specifies the use of Arcfour (also known as RC4), a fast stream
cipher. As [<a href="./rfc4253" title=""The Secure Shell (SSH) Transport Layer Protocol"">RFC4253</a>] says, though, "Arcfour (and RC4) has problems
with weak keys, and should be used with caution." These problems are
described in more detail in [<a href="#ref-MANTIN01" title=""Analysis of the Stream Cipher RC4"">MANTIN01</a>], along with a recommendation
to discard the first 1536 bytes of keystream so as to ensure that the
cipher's internal state is thoroughly mixed. This document specifies
new cipher algorithms for SSH that follow this recommendation.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in this Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Harris Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4345">RFC 4345</a> Improved Arcfour Modes for SSH January 2006</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Applicability Statement</span>
Implementations of Arcfour are typically slightly faster and much
smaller than those of any other encryption algorithm currently
defined for SSH. This must be balanced, though, against the known
security problems with Arcfour described in <a href="#section-5">Section 5</a>. In most
cases, where speed and code size are not critical issues, the
algorithms specified by [<a href="./rfc4344" title=""The Secure Shell (SSH) Transport Layer Encryption Modes"">RFC4344</a>] should be used instead.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Algorithm Definitions</span>
The "arcfour128" algorithm is the RC4 cipher, as described in
[<a href="#ref-SCHNEIER" title=""Applied Cryptography Second Edition: protocols algorithms and source in code in C"">SCHNEIER</a>], using a 128-bit key. The first 1536 bytes of keystream
generated by the cipher MUST be discarded, and the first byte of the
first encrypted packet MUST be encrypted using the 1537th byte of
keystream.
The "arcfour256" algorithm is the same, but uses a 256-bit key.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The security considerations in [<a href="./rfc4251" title=""The Secure Shell (SSH) Protocol Architecture"">RFC4251</a>] apply.
The discarded bytes of keystream MUST be kept secret and MUST NOT be
transmitted over the network. The contents of these bytes could
reveal information about the key.
There are two classes of attack on Arcfour described in [<a href="#ref-MIRONOV" title=""(Not So) Random Shuffles of RC4"">MIRONOV</a>].
Strong distinguishers distinguish an Arcfour keystream from
randomness at the start of the stream and are defended against by the
algorithm defined in this document. Weak distinguishers can operate
on any part of the keystream, and the best ones, described in [<a href="#ref-FMcG" title=""Statistical Analysis of the Alleged RC4 Keystream Generator"">FMcG</a>]
and [<a href="#ref-MANTIN05" title=""Predicting and Distinguishing Attacks on RC4 Keystream Generator"">MANTIN05</a>], can use data from multiple, different keystreams. A
consequence of this is that encrypting the same data (for instance, a
password) sufficiently many times in separate Arcfour keystreams can
be sufficient to leak information about it to an adversary. It is
thus RECOMMENDED that Arcfour (either in the form described here or
that described in [<a href="./rfc4251" title=""The Secure Shell (SSH) Protocol Architecture"">RFC4251</a>]) not be used for high-volume password-
authenticated connections.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
The IANA has assigned the Encryption Algorithm Names "arcfour128" and
"arcfour256" in accordance with [<a href="./rfc4250" title=""The Secure Shell (SSH) Protocol Assigned Numbers"">RFC4250</a>].
<span class="grey">Harris Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4345">RFC 4345</a> Improved Arcfour Modes for SSH January 2006</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4250">RFC4250</a>] Lehtinen, S. and C. Lonvick, Ed., "The Secure Shell (SSH)
Protocol Assigned Numbers", <a href="./rfc4250">RFC 4250</a>, January 2006.
[<a id="ref-RFC4251">RFC4251</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Protocol Architecture", <a href="./rfc4251">RFC 4251</a>, January 2006.
[<a id="ref-RFC4253">RFC4253</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Transport Layer Protocol", <a href="./rfc4253">RFC 4253</a>, January 2006
[<a id="ref-RFC4344">RFC4344</a>] Bellare, M., Kohno, T., and C. Namprempre, "The Secure
Shell (SSH) Transport Layer Encryption Modes", <a href="./rfc4344">RFC 4344</a>,
January 2006.
[<a id="ref-SCHNEIER">SCHNEIER</a>] Schneier, B., "Applied Cryptography Second Edition:
protocols algorithms and source in code in C", John Wiley
and Sons, New York, NY, 1996.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-FMcG">FMcG</a>] Fluhrer, S. and D. McGrew, "Statistical Analysis of the
Alleged RC4 Keystream Generator", Fast Software
Encryption: 7th International Workshop, FSE 2000, April
2000, <<a href="http://www.mindspring.com/~dmcgrew/rc4-03.pdf">http://www.mindspring.com/~dmcgrew/rc4-03.pdf</a>>.
[<a id="ref-MANTIN01">MANTIN01</a>] Mantin, I., "Analysis of the Stream Cipher RC4", M.Sc.
Thesis, Weizmann Institute of Science, 2001, <<a href="http://www.wisdom.weizmann.ac.il/~itsik/RC4/Papers/Mantin1.zip">http://</a>
<a href="http://www.wisdom.weizmann.ac.il/~itsik/RC4/Papers/Mantin1.zip">www.wisdom.weizmann.ac.il/~itsik/RC4/Papers/Mantin1.zip</a>>.
[<a id="ref-MIRONOV">MIRONOV</a>] Mironov, I., "(Not So) Random Shuffles of RC4", Advances
in Cryptology -- CRYPTO 2002: 22nd Annual International
Cryptology Conference, August 2002,
<<a href="http://eprint.iacr.org/2002/067.pdf">http://eprint.iacr.org/2002/067.pdf</a>>.
[<a id="ref-MANTIN05">MANTIN05</a>] Mantin, I., "Predicting and Distinguishing Attacks on RC4
Keystream Generator", Advances in Cryptology -- EUROCRYPT
2005: 24th Annual International Conference on the Theory
and Applications of Cryptographic Techniques, May 2005.
<span class="grey">Harris Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4345">RFC 4345</a> Improved Arcfour Modes for SSH January 2006</span>
Author's Address
Ben Harris
2a Eachard Road
CAMBRIDGE
CB3 0HY
UNITED KINGDOM
EMail: bjh21@bjh21.me.uk
Trademark Notice
"RC4" and "SSH" are registered trademarks in the United States.
<span class="grey">Harris Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4345">RFC 4345</a> Improved Arcfour Modes for SSH January 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Harris Standards Track [Page 5]
</pre>
|
