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
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
|
<pre>Network Working Group S. Lehtinen
Request for Comments: 4250 SSH Communications Security Corp
Category: Standards Track C. Lonvick, Ed.
Cisco Systems, Inc.
January 2006
<span class="h1">The Secure Shell (SSH) Protocol Assigned Numbers</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 defines the instructions to the IANA and the initial
state of the IANA assigned numbers for the Secure Shell (SSH)
protocol. It is intended only for the initialization of the IANA
registries referenced in the set of SSH documents.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Contributors ....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Conventions Used in This Document ...............................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. <a href="./rfc2119">RFC 2119</a> Keywords ..........................................<a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. <a href="./rfc2434">RFC 2434</a> Keywords ..........................................<a href="#page-3">3</a>
<a href="#section-3.3">3.3</a>. Protocol Fields and Values .................................<a href="#page-4">4</a>
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Message Numbers ............................................<a href="#page-5">5</a>
<a href="#section-4.1.1">4.1.1</a>. Conventions .........................................<a href="#page-5">5</a>
<a href="#section-4.1.2">4.1.2</a>. Initial Assignments .................................<a href="#page-6">6</a>
<a href="#section-4.1.3">4.1.3</a>. Future Assignments ..................................<a href="#page-6">6</a>
<a href="#section-4.2">4.2</a>. Disconnection Messages Reason Codes and Descriptions .......<a href="#page-7">7</a>
<a href="#section-4.2.1">4.2.1</a>. Conventions .........................................<a href="#page-7">7</a>
<a href="#section-4.2.2">4.2.2</a>. Initial Assignments .................................<a href="#page-7">7</a>
<a href="#section-4.2.3">4.2.3</a>. Future Assignments ..................................<a href="#page-8">8</a>
<a href="#section-4.3">4.3</a>. Channel Connection Failure Reason Codes and Descriptions ...<a href="#page-8">8</a>
<a href="#section-4.3.1">4.3.1</a>. Conventions .........................................<a href="#page-8">8</a>
<a href="#section-4.3.2">4.3.2</a>. Initial Assignments .................................<a href="#page-8">8</a>
<span class="grey">Lehtinen & Lonvick Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<a href="#section-4.3.3">4.3.3</a>. Future Assignments ..................................<a href="#page-8">8</a>
<a href="#section-4.3.4">4.3.4</a>. Notes about the PRIVATE USE Range ...................<a href="#page-9">9</a>
<a href="#section-4.4">4.4</a>. Extended Channel Data Transfer data_type_code and Data .....<a href="#page-9">9</a>
<a href="#section-4.4.1">4.4.1</a>. Conventions .........................................<a href="#page-9">9</a>
<a href="#section-4.4.2">4.4.2</a>. Initial Assignments ................................<a href="#page-10">10</a>
<a href="#section-4.4.3">4.4.3</a>. Future Assignments .................................<a href="#page-10">10</a>
<a href="#section-4.5">4.5</a>. Pseudo-Terminal Encoded Terminal Modes ....................<a href="#page-10">10</a>
<a href="#section-4.5.1">4.5.1</a>. Conventions ........................................<a href="#page-10">10</a>
<a href="#section-4.5.2">4.5.2</a>. Initial Assignments ................................<a href="#page-10">10</a>
<a href="#section-4.5.3">4.5.3</a>. Future Assignments .................................<a href="#page-12">12</a>
<a href="#section-4.6">4.6</a>. Names .....................................................<a href="#page-12">12</a>
<a href="#section-4.6.1">4.6.1</a>. Conventions for Names ..............................<a href="#page-13">13</a>
<a href="#section-4.6.2">4.6.2</a>. Future Assignments of Names ........................<a href="#page-13">13</a>
<a href="#section-4.7">4.7</a>. Service Names .............................................<a href="#page-13">13</a>
<a href="#section-4.8">4.8</a>. Authentication Method Names ...............................<a href="#page-14">14</a>
<a href="#section-4.9">4.9</a>. Connection Protocol Assigned Names ........................<a href="#page-14">14</a>
<a href="#section-4.9.1">4.9.1</a>. Connection Protocol Channel Types ..................<a href="#page-14">14</a>
<a href="#section-4.9.2">4.9.2</a>. Connection Protocol Global Request Names ...........<a href="#page-14">14</a>
<a href="#section-4.9.3">4.9.3</a>. Connection Protocol Channel Request Names ..........<a href="#page-15">15</a>
<a href="#section-4.9.4">4.9.4</a>. Initial Assignment of Signal Names .................<a href="#page-15">15</a>
<a href="#section-4.9.5">4.9.5</a>. Connection Protocol Subsystem Names ................<a href="#page-15">15</a>
<a href="#section-4.10">4.10</a>. Key Exchange Method Names ................................<a href="#page-16">16</a>
<a href="#section-4.11">4.11</a>. Assigned Algorithm Names .................................<a href="#page-16">16</a>
<a href="#section-4.11.1">4.11.1</a>. Encryption Algorithm Names ........................<a href="#page-16">16</a>
<a href="#section-4.11.2">4.11.2</a>. MAC Algorithm Names ...............................<a href="#page-17">17</a>
<a href="#section-4.11.3">4.11.3</a>. Public Key Algorithm Names ........................<a href="#page-17">17</a>
<a href="#section-4.11.4">4.11.4</a>. Compression Algorithm Names .......................<a href="#page-17">17</a>
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-17">17</a>
<a href="#section-6">6</a>. References .....................................................<a href="#page-18">18</a>
<a href="#section-6.1">6.1</a>. Normative References ......................................<a href="#page-18">18</a>
<a href="#section-6.2">6.2</a>. Informative References ....................................<a href="#page-18">18</a>
Authors' Addresses ................................................<a href="#page-19">19</a>
Trademark Notice ..................................................<a href="#page-19">19</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document does not define any new protocols. It is intended only
to create the initial state of the IANA databases for the SSH
protocol and also contains instructions for future assignments.
Except for one HISTORIC algorithm generally regarded as obsolete,
this document does not define any new protocols or number ranges not
already defined in: [<a href="#ref-SSH-ARCH" title=""The Secure Shell (SSH) Protocol Architecture"">SSH-ARCH</a>], [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>], [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>],
[<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>].
<span class="grey">Lehtinen & Lonvick Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Contributors</span>
The major original contributors of this set of documents have been:
Tatu Ylonen, Tero Kivinen, Timo J. Rinne, Sami Lehtinen (all of SSH
Communications Security Corp), and Markku-Juhani O. Saarinen
(University of Jyvaskyla). Darren Moffat was the original editor of
this set of documents and also made very substantial contributions.
Many people contributed to the development of this document over the
years. People who should be acknowledged include Mats Andersson, Ben
Harris, Bill Sommerfeld, Brent McClure, Niels Moller, Damien Miller,
Derek Fawcus, Frank Cusack, Heikki Nousiainen, Jakob Schlyter, Jeff
Van Dyke, Jeffrey Altman, Jeffrey Hutzelman, Jon Bright, Joseph
Galbraith, Ken Hornstein, Markus Friedl, Martin Forssen, Nicolas
Williams, Niels Provos, Perry Metzger, Peter Gutmann, Simon
Josefsson, Simon Tatham, Wei Dai, Denis Bider, der Mouse, and
Tadayoshi Kohno. Listing their names here does not mean that they
endorse this document, but that they have contributed to it.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Conventions Used in This Document</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. <a href="./rfc2119">RFC 2119</a> Keywords</span>
All documents related to the SSH protocols shall use the keywords
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" to describe
requirements. These keywords 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="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. <a href="./rfc2434">RFC 2434</a> Keywords</span>
The keywords "PRIVATE USE", "HIERARCHICAL ALLOCATION", "FIRST COME
FIRST SERVED", "EXPERT REVIEW", "SPECIFICATION REQUIRED", "IESG
APPROVAL", "IETF CONSENSUS", and "STANDARDS ACTION" that appear in
this document when used to describe namespace allocation are to be
interpreted as described in [<a href="./rfc2434" title="">RFC2434</a>]. These designations are
repeated in this document for clarity.
PRIVATE USE - For private or local use only, with the type and
purpose defined by the local site. No attempt is made to prevent
multiple sites from using the same value in different (and
incompatible) ways. There is no need for IANA to review such
assignments and assignments are not generally useful for
interoperability.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
HIERARCHICAL ALLOCATION - Delegated managers can assign values
provided they have been given control over that part of the name
space. IANA controls the higher levels of the namespace according to
one of the other policies.
FIRST COME FIRST SERVED - Anyone can obtain an assigned number, so
long as they provide a point of contact and a brief description of
what the value would be used for. For numbers, the exact value is
generally assigned by the IANA; with names, specific names are
usually requested.
EXPERT REVIEW - approval by a Designated Expert is required.
SPECIFICATION REQUIRED - Values and their meaning must be documented
in an RFC or other permanent and readily available reference, in
sufficient detail so that interoperability between independent
implementations is possible.
IESG APPROVAL - New assignments must be approved by the IESG, but
there is no requirement that the request be documented in an RFC
(though the IESG has discretion to request documents or other
supporting materials on a case-by-case basis).
IETF CONSENSUS - New values are assigned through the IETF consensus
process. Specifically, new assignments are made via RFCs approved by
the IESG. Typically, the IESG will seek input on prospective
assignments from appropriate persons (e.g., a relevant Working Group
if one exists).
STANDARDS ACTION - Values are assigned only for Standards Track RFCs
approved by the IESG.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Protocol Fields and Values</span>
Protocol fields and possible values to fill them are defined in this
set of documents. Protocol fields will be defined in the message
definitions. As an example, SSH_MSG_CHANNEL_DATA is defined as
follows.
byte SSH_MSG_CHANNEL_DATA
uint32 recipient channel
string data
Throughout these documents, when the fields are referenced, they will
appear within single quotes. When values to fill those fields are
referenced, they will appear within double quotes. Using the above
example, possible values for 'data' are "foo" and "bar".
<span class="grey">Lehtinen & Lonvick Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This entire document is the IANA considerations for the SSH protocol,
as defined in [<a href="#ref-SSH-ARCH" title=""The Secure Shell (SSH) Protocol Architecture"">SSH-ARCH</a>], [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>], [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>], [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>].
This section contains conventions used in naming the namespaces, the
initial state of the registry, and instructions for future
assignments.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Message Numbers</span>
The Message Number is a byte value that describes the payload of a
packet.
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. Conventions</span>
Protocol packets have message numbers in the range 1 to 255. These
numbers are allocated as follows:
Transport layer protocol:
1 to 19 Transport layer generic (e.g., disconnect, ignore,
debug, etc.)
20 to 29 Algorithm negotiation
30 to 49 Key exchange method specific (numbers can be reused
for different authentication methods)
User authentication protocol:
50 to 59 User authentication generic
60 to 79 User authentication method specific (numbers can be
reused for different authentication methods)
Connection protocol:
80 to 89 Connection protocol generic
90 to 127 Channel related messages
Reserved for client protocols:
128 to 191 Reserved
Local extensions:
192 to 255 Local extensions
<span class="grey">Lehtinen & Lonvick Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. Initial Assignments</span>
The following table identifies the initial assignments of the Message
ID values.
Message ID Value Reference
----------- ----- ---------
SSH_MSG_DISCONNECT 1 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_IGNORE 2 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_UNIMPLEMENTED 3 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_DEBUG 4 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_SERVICE_REQUEST 5 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_SERVICE_ACCEPT 6 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_KEXINIT 20 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_NEWKEYS 21 [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>]
SSH_MSG_USERAUTH_REQUEST 50 [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]
SSH_MSG_USERAUTH_FAILURE 51 [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]
SSH_MSG_USERAUTH_SUCCESS 52 [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]
SSH_MSG_USERAUTH_BANNER 53 [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]
SSH_MSG_GLOBAL_REQUEST 80 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_REQUEST_SUCCESS 81 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_REQUEST_FAILURE 82 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_OPEN 90 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_OPEN_CONFIRMATION 91 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_OPEN_FAILURE 92 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_WINDOW_ADJUST 93 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_DATA 94 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_EXTENDED_DATA 95 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_EOF 96 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_CLOSE 97 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_REQUEST 98 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_SUCCESS 99 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SSH_MSG_CHANNEL_FAILURE 100 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. Future Assignments</span>
Requests for assignments of new message numbers in the range of 1 to
29, 50 to 59, and 80 to 127 MUST be done through the STANDARDS ACTION
method, as described in [<a href="./rfc2434" title="">RFC2434</a>].
The meanings of message numbers in the range of 30 to 49 are specific
to the key exchange method in use, and their meaning will be
specified by the definition of that method.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
The meanings of message numbers in the range of 60 to 79 are specific
to the user authentication method in use, and their meaning will be
specified by the definition of that method.
Requests for assignments of new message numbers in the range of 128
to 191 MUST be done through the IETF CONSENSUS method, as described
in [<a href="./rfc2434" title="">RFC2434</a>].
The IANA will not control the message numbers in the range of 192
through 255. This range will be left for PRIVATE USE.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Disconnection Messages Reason Codes and Descriptions</span>
The Disconnection Message 'reason code' is a uint32 value. The
associated Disconnection Message 'description' is a human-readable
message that describes the disconnect reason.
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Conventions</span>
Protocol packets containing the SSH_MSG_DISCONNECT message MUST have
Disconnection Message 'reason code' values in the range of 0x00000001
to 0xFFFFFFFF. These are described in [<a href="#ref-SSH-TRANS" title=""The Secure Shell (SSH) Transport Layer Protocol"">SSH-TRANS</a>].
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Initial Assignments</span>
The following table identifies the initial assignments of the
SSH_MSG_DISCONNECT 'description' and 'reason code' values.
Symbolic Name reason code
------------- -----------
SSH_DISCONNECT_HOST_NOT_ALLOWED_TO_CONNECT 1
SSH_DISCONNECT_PROTOCOL_ERROR 2
SSH_DISCONNECT_KEY_EXCHANGE_FAILED 3
SSH_DISCONNECT_RESERVED 4
SSH_DISCONNECT_MAC_ERROR 5
SSH_DISCONNECT_COMPRESSION_ERROR 6
SSH_DISCONNECT_SERVICE_NOT_AVAILABLE 7
SSH_DISCONNECT_PROTOCOL_VERSION_NOT_SUPPORTED 8
SSH_DISCONNECT_HOST_KEY_NOT_VERIFIABLE 9
SSH_DISCONNECT_CONNECTION_LOST 10
SSH_DISCONNECT_BY_APPLICATION 11
SSH_DISCONNECT_TOO_MANY_CONNECTIONS 12
SSH_DISCONNECT_AUTH_CANCELLED_BY_USER 13
SSH_DISCONNECT_NO_MORE_AUTH_METHODS_AVAILABLE 14
SSH_DISCONNECT_ILLEGAL_USER_NAME 15
<span class="grey">Lehtinen & Lonvick Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Future Assignments</span>
Disconnection Message 'reason code' values MUST be assigned
sequentially. Requests for assignments of new Disconnection Message
'reason code' values, and their associated Disconnection Message
'description' text, in the range of 0x00000010 through 0xFDFFFFFF,
MUST be done through the IETF CONSENSUS method, as described in
[<a href="./rfc2434" title="">RFC2434</a>]. The IANA will not assign Disconnection Message 'reason
code' values in the range of 0xFE000000 through 0xFFFFFFFF.
Disconnection Message 'reason code' values in that range are left for
PRIVATE USE, as described in [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Channel Connection Failure Reason Codes and Descriptions</span>
The Channel Connection Failure 'reason code' is a uint32 value. The
associated Channel Connection Failure 'description' text is a human-
readable message that describes the channel connection failure
reason. This is described in [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>].
<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. Conventions</span>
Protocol packets containing the SSH_MSG_CHANNEL_OPEN_FAILURE message
MUST have Channel Connection Failure 'reason code' values in the
range of 0x00000001 to 0xFFFFFFFF.
<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. Initial Assignments</span>
The initial assignments for the 'reason code' values and
'description' values are given in the table below. Note that the
values for the 'reason code' are given in decimal format for
readability, but they are actually uint32 values.
Symbolic Name reason code
------------- -----------
SSH_OPEN_ADMINISTRATIVELY_PROHIBITED 1
SSH_OPEN_CONNECT_FAILED 2
SSH_OPEN_UNKNOWN_CHANNEL_TYPE 3
SSH_OPEN_RESOURCE_SHORTAGE 4
<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. Future Assignments</span>
Channel Connection Failure 'reason code' values MUST be assigned
sequentially. Requests for assignments of new Channel Connection
Failure 'reason code' values, and their associated Channel Connection
Failure 'description string', in the range of 0x00000005 to
0xFDFFFFFF MUST be done through the IETF CONSENSUS method, as
described in [<a href="./rfc2434" title="">RFC2434</a>]. The IANA will not assign Channel Connection
<span class="grey">Lehtinen & Lonvick Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
Failure 'reason code' values in the range of 0xFE000000 to
0xFFFFFFFF. Channel Connection Failure 'reason code' values in that
range are left for PRIVATE USE, as described in [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a>. Notes about the PRIVATE USE Range</span>
While it is understood that the IANA will have no control over the
range of 0xFE000000 to 0xFFFFFFFF, this range will be split in two
parts and administered by the following conventions.
o The range of 0xFE000000 to 0xFEFFFFFF is to be used in conjunction
with locally assigned channels. For example, if a channel is
proposed with a 'channel type' of "example_session@example.com"
but fails, then the server will respond with either a 'reason
code' assigned by the IANA (as listed above and in the range of
0x00000001 to 0xFDFFFFFF), or with a locally assigned value in the
range of 0xFE000000 to 0xFEFFFFFF. Naturally, if the server does
not understand the proposed 'channel type', even if it is a
locally defined 'channel type', then the 'reason code' MUST be
0x00000003, as described above. If the server does understand the
'channel type', but the channel still fails to open, then the
server SHOULD respond with a locally assigned 'reason code' value
that is consistent with the proposed local 'channel type'. It is
assumed that practitioners will first attempt to use the IANA-
assigned 'reason code' values and then document their locally
assigned 'reason code' values.
o There are no restrictions or suggestions for the range starting
with 0xFF. No interoperability is expected for anything used in
this range. Essentially, it is for experimentation.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Extended Channel Data Transfer data_type_code and Data</span>
The Extended Channel Data Transfer 'data_type_code' is a uint32
value. The associated Extended Channel Data Transfer 'data' is a
human-readable message that describes the type of data allowed to be
transferred in the channel.
<span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>. Conventions</span>
Protocol packets containing the SSH_MSG_CHANNEL_EXTENDED_DATA message
MUST have Extended Channel Data Transfer 'data_type_code' values in
the range of 0x00000001 to 0xFFFFFFFF. This is described in
[<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>].
<span class="grey">Lehtinen & Lonvick Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>. Initial Assignments</span>
The initial assignments for the 'data_type_code' values and 'data'
values are given in the table below. Note that the value for the
'data_type_code' is given in decimal format for readability, but the
values are actually uint32 values.
Symbolic name data_type_code
------------- --------------
SSH_EXTENDED_DATA_STDERR 1
<span class="h4"><a class="selflink" id="section-4.4.3" href="#section-4.4.3">4.4.3</a>. Future Assignments</span>
Extended Channel Data Transfer 'data_type_code' values MUST be
assigned sequentially. Requests for assignments of new Extended
Channel Data Transfer 'data_type_code' values, and their associated
Extended Channel Data Transfer 'data' strings, in the range of
0x00000002 to 0xFDFFFFFF, MUST be done through the IETF CONSENSUS
method, as described in [<a href="./rfc2434" title="">RFC2434</a>]. The IANA will not assign Extended
Channel Data Transfer 'data_type_code' values in the range of
0xFE000000 to 0xFFFFFFFF. Extended Channel Data Transfer
'data_type_code' values in that range are left for PRIVATE USE, as
described in [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Pseudo-Terminal Encoded Terminal Modes</span>
SSH_MSG_CHANNEL_REQUEST messages with a "pty-req" string MUST contain
'encoded terminal modes'. The 'encoded terminal modes' value is a
byte stream of opcode-argument pairs.
<span class="h4"><a class="selflink" id="section-4.5.1" href="#section-4.5.1">4.5.1</a>. Conventions</span>
Protocol packets containing the SSH_MSG_CHANNEL_REQUEST message with
a "pty-req" string MUST contain an 'encoded terminal modes' value.
The opcode values consist of a single byte and are in the range of 1
to 255. Opcodes 1 to 159 have a uint32 argument. Opcodes 160 to 255
are not yet defined.
<span class="h4"><a class="selflink" id="section-4.5.2" href="#section-4.5.2">4.5.2</a>. Initial Assignments</span>
The following table identifies the initial assignments of the opcode
values that are used in the 'encoded terminal modes' value.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
opcode mnemonic description
------ -------- -----------
0 TTY_OP_END Indicates end of options.
1 VINTR Interrupt character; 255 if none. Similarly
for the other characters. Not all of these
characters are supported on all systems.
2 VQUIT The quit character (sends SIGQUIT signal on
POSIX systems).
3 VERASE Erase the character to left of the cursor.
4 VKILL Kill the current input line.
5 VEOF End-of-file character (sends EOF from the
terminal).
6 VEOL End-of-line character in addition to
carriage return and/or linefeed.
7 VEOL2 Additional end-of-line character.
8 VSTART Continues paused output (normally
control-Q).
9 VSTOP Pauses output (normally control-S).
10 VSUSP Suspends the current program.
11 VDSUSP Another suspend character.
12 VREPRINT Reprints the current input line.
13 VWERASE Erases a word left of cursor.
14 VLNEXT Enter the next character typed literally,
even if it is a special character
15 VFLUSH Character to flush output.
16 VSWTCH Switch to a different shell layer.
17 VSTATUS Prints system status line (load, command,
pid, etc).
18 VDISCARD Toggles the flushing of terminal output.
30 IGNPAR The ignore parity flag. The parameter
SHOULD be 0 if this flag is FALSE,
and 1 if it is TRUE.
31 PARMRK Mark parity and framing errors.
32 INPCK Enable checking of parity errors.
33 ISTRIP Strip 8th bit off characters.
34 INLCR Map NL into CR on input.
35 IGNCR Ignore CR on input.
36 ICRNL Map CR to NL on input.
37 IUCLC Translate uppercase characters to
lowercase.
38 IXON Enable output flow control.
39 IXANY Any char will restart after stop.
40 IXOFF Enable input flow control.
41 IMAXBEL Ring bell on input queue full.
50 ISIG Enable signals INTR, QUIT, [D]SUSP.
51 ICANON Canonicalize input lines.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
52 XCASE Enable input and output of uppercase
characters by preceding their lowercase
equivalents with "\".
53 ECHO Enable echoing.
54 ECHOE Visually erase chars.
55 ECHOK Kill character discards current line.
56 ECHONL Echo NL even if ECHO is off.
57 NOFLSH Don't flush after interrupt.
58 TOSTOP Stop background jobs from output.
59 IEXTEN Enable extensions.
60 ECHOCTL Echo control characters as ^(Char).
61 ECHOKE Visual erase for line kill.
62 PENDIN Retype pending input.
70 OPOST Enable output processing.
71 OLCUC Convert lowercase to uppercase.
72 ONLCR Map NL to CR-NL.
73 OCRNL Translate carriage return to newline
(output).
74 ONOCR Translate newline to carriage
return-newline (output).
75 ONLRET Newline performs a carriage return
(output).
90 CS7 7 bit mode.
91 CS8 8 bit mode.
92 PARENB Parity enable.
93 PARODD Odd parity, else even.
128 TTY_OP_ISPEED Specifies the input baud rate in
bits per second.
129 TTY_OP_OSPEED Specifies the output baud rate in
bits per second.
<span class="h4"><a class="selflink" id="section-4.5.3" href="#section-4.5.3">4.5.3</a>. Future Assignments</span>
Requests for assignments of new opcodes and their associated
arguments MUST be done through the IETF CONSENSUS method, as
described in [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Names</span>
In the following sections, the values for the name spaces are
textual. The conventions and instructions to the IANA for future
assignments are given in this section. The initial assignments are
given in their respective sections.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.6.1" href="#section-4.6.1">4.6.1</a>. Conventions for Names</span>
All names registered by the IANA in the following sections MUST be
printable US-ASCII strings, and MUST NOT contain the characters at-
sign ("@"), comma (","), whitespace, control characters (ASCII codes
32 or less), or the ASCII code 127 (DEL). Names are case-sensitive,
and MUST NOT be longer than 64 characters.
A provision is made here for locally extensible names. The IANA will
not register, and will not control, names with the at-sign in them.
Names with the at-sign in them will have the format of
"name@domainname" (without the double quotes) where the part
preceding the at-sign is the name. The format of the part preceding
the at-sign is not specified; however, these names MUST be printable
US-ASCII strings, and MUST NOT contain the comma character (","),
whitespace, control characters (ASCII codes 32 or less), or the ASCII
code 127 (DEL). They MUST have only a single at-sign in them. The
part following the at-sign MUST be a valid, fully qualified internet
domain name [<a href="./rfc1034" title=""Domain names - concepts and facilities"">RFC1034</a>] controlled by the person or organization
defining the name. Names are case-sensitive, and MUST NOT be longer
than 64 characters. It is up to each domain how it manages its local
namespace. It has been noted that these names resemble STD 11
[<a href="./rfc0822" title=""Standard for the format of ARPA Internet text messages"">RFC0822</a>] email addresses. This is purely coincidental and has
nothing to do with STD 11 [<a href="./rfc0822" title=""Standard for the format of ARPA Internet text messages"">RFC0822</a>]. An example of a locally defined
name is "ourcipher-cbc@example.com" (without the double quotes).
<span class="h4"><a class="selflink" id="section-4.6.2" href="#section-4.6.2">4.6.2</a>. Future Assignments of Names</span>
Requests for assignments of new names MUST be done through the IETF
CONSENSUS method, as described in [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. Service Names</span>
The 'service name' is used to describe a protocol layer. The
following table lists the initial assignments of the 'service name'
values.
Service Name Reference
------------- ---------
ssh-userauth [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]
ssh-connection [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
<span class="grey">Lehtinen & Lonvick Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. Authentication Method Names</span>
The Authentication Method Name is used to describe an authentication
method for the "ssh-userauth" service [<a href="#ref-SSH-USERAUTH" title=""The Secure Shell (SSH) Authentication Protocol"">SSH-USERAUTH</a>]. The following
table identifies the initial assignments of the Authentication Method
Names.
Method Name Reference
------------ ---------
publickey [SSH-USERAUTH, <a href="#section-7">Section 7</a>]
password [SSH-USERAUTH, <a href="#section-8">Section 8</a>]
hostbased [SSH-USERAUTH, <a href="#section-9">Section 9</a>]
none [SSH-USERAUTH, <a href="#section-5.2">Section 5.2</a>]
<span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>. Connection Protocol Assigned Names</span>
The following table lists the initial assignments to the Connection
Protocol Type and Request names.
<span class="h4"><a class="selflink" id="section-4.9.1" href="#section-4.9.1">4.9.1</a>. Connection Protocol Channel Types</span>
The following table lists the initial assignments of the Connection
Protocol Channel Types.
Channel type Reference
------------ ---------
session [SSH-CONNECT, <a href="#section-6.1">Section 6.1</a>]
x11 [SSH-CONNECT, <a href="#section-6.3.2">Section 6.3.2</a>]
forwarded-tcpip [SSH-CONNECT, <a href="#section-7.2">Section 7.2</a>]
direct-tcpip [SSH-CONNECT, <a href="#section-7.2">Section 7.2</a>]
<span class="h4"><a class="selflink" id="section-4.9.2" href="#section-4.9.2">4.9.2</a>. Connection Protocol Global Request Names</span>
The following table lists the initial assignments of the Connection
Protocol Global Request Names.
Request type Reference
------------ ---------
tcpip-forward [SSH-CONNECT, <a href="#section-7.1">Section 7.1</a>]
cancel-tcpip-forward [SSH-CONNECT, <a href="#section-7.1">Section 7.1</a>]
<span class="grey">Lehtinen & Lonvick Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.9.3" href="#section-4.9.3">4.9.3</a>. Connection Protocol Channel Request Names</span>
The following table lists the initial assignments of the Connection
Protocol Channel Request Names.
Request type Reference
------------ ---------
pty-req [SSH-CONNECT, <a href="#section-6.2">Section 6.2</a>]
x11-req [SSH-CONNECT, <a href="#section-6.3.1">Section 6.3.1</a>]
env [SSH-CONNECT, <a href="#section-6.4">Section 6.4</a>]
shell [SSH-CONNECT, <a href="#section-6.5">Section 6.5</a>]
exec [SSH-CONNECT, <a href="#section-6.5">Section 6.5</a>]
subsystem [SSH-CONNECT, <a href="#section-6.5">Section 6.5</a>]
window-change [SSH-CONNECT, <a href="#section-6.7">Section 6.7</a>]
xon-xoff [SSH-CONNECT, <a href="#section-6.8">Section 6.8</a>]
signal [SSH-CONNECT, <a href="#section-6.9">Section 6.9</a>]
exit-status [SSH-CONNECT, <a href="#section-6.10">Section 6.10</a>]
exit-signal [SSH-CONNECT, <a href="#section-6.10">Section 6.10</a>]
<span class="h4"><a class="selflink" id="section-4.9.4" href="#section-4.9.4">4.9.4</a>. Initial Assignment of Signal Names</span>
The following table lists the initial assignments of the Signal
Names.
Signal Reference
------ ---------
ABRT [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
ALRM [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
FPE [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
HUP [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
ILL [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
INT [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
KILL [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
PIPE [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
QUIT [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
SEGV [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
TERM [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
USR1 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
USR2 [<a href="#ref-SSH-CONNECT" title=""The Secure Shell (SSH) Connection Protocol"">SSH-CONNECT</a>]
<span class="h4"><a class="selflink" id="section-4.9.5" href="#section-4.9.5">4.9.5</a>. Connection Protocol Subsystem Names</span>
There are no initial assignments of the Connection Protocol Subsystem
Names.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h3"><a class="selflink" id="section-4.10" href="#section-4.10">4.10</a>. Key Exchange Method Names</span>
The name "diffie-hellman-group1-sha1" is used for a key exchange
method using an Oakley group, as defined in [<a href="./rfc2409" title=""The Internet Key Exchange (IKE)"">RFC2409</a>]. SSH maintains
its own group identifier space, which is logically distinct from
Oakley [<a href="./rfc2412" title=""The OAKLEY Key Determination Protocol"">RFC2412</a>] and IKE; however, for one additional group, the
Working Group adopted the number assigned by [<a href="./rfc3526" title=""More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)"">RFC3526</a>], using
"diffie-hellman-group14-sha1" for the name of the second defined
group. Implementations should treat these names as opaque
identifiers and should not assume any relationship between the groups
used by SSH and the groups defined for IKE.
The following table identifies the initial assignments of the key
exchange methods.
Method name Reference
------------ ---------
diffie-hellman-group1-sha1 [SSH-TRANS, <a href="#section-8.1">Section 8.1</a>]
diffie-hellman-group14-sha1 [SSH-TRANS, <a href="#section-8.2">Section 8.2</a>]
<span class="h3"><a class="selflink" id="section-4.11" href="#section-4.11">4.11</a>. Assigned Algorithm Names</span>
<span class="h4"><a class="selflink" id="section-4.11.1" href="#section-4.11.1">4.11.1</a>. Encryption Algorithm Names</span>
The following table identifies the initial assignment of the
Encryption Algorithm Names.
Encryption Algorithm Name Reference
------------------------- ---------
3des-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
blowfish-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
twofish256-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
twofish-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
twofish192-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
twofish128-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
aes256-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
aes192-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
aes128-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
serpent256-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
serpent192-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
serpent128-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
arcfour [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
idea-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
cast128-cbc [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
none [SSH-TRANS, <a href="#section-6.3">Section 6.3</a>]
des-cbc [<a href="#ref-FIPS-46-3" title=""Data Encryption Standard (DES)"">FIPS-46-3</a>] HISTORIC; See
page 4 of [<a href="#ref-FIPS-46-3" title=""Data Encryption Standard (DES)"">FIPS-46-3</a>]
<span class="grey">Lehtinen & Lonvick Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h4"><a class="selflink" id="section-4.11.2" href="#section-4.11.2">4.11.2</a>. MAC Algorithm Names</span>
The following table identifies the initial assignments of the MAC
Algorithm Names.
MAC Algorithm Name Reference
------------------ ---------
hmac-sha1 [SSH-TRANS, <a href="#section-6.4">Section 6.4</a>]
hmac-sha1-96 [SSH-TRANS, <a href="#section-6.4">Section 6.4</a>]
hmac-md5 [SSH-TRANS, <a href="#section-6.4">Section 6.4</a>]
hmac-md5-96 [SSH-TRANS, <a href="#section-6.4">Section 6.4</a>]
none [SSH-TRANS, <a href="#section-6.4">Section 6.4</a>]
<span class="h4"><a class="selflink" id="section-4.11.3" href="#section-4.11.3">4.11.3</a>. Public Key Algorithm Names</span>
The following table identifies the initial assignments of the Public
Key Algorithm names.
Public Key Algorithm Name Reference
------------------------- ---------
ssh-dss [SSH-TRANS, <a href="#section-6.6">Section 6.6</a>]
ssh-rsa [SSH-TRANS, <a href="#section-6.6">Section 6.6</a>]
pgp-sign-rsa [SSH-TRANS, <a href="#section-6.6">Section 6.6</a>]
pgp-sign-dss [SSH-TRANS, <a href="#section-6.6">Section 6.6</a>]
<span class="h4"><a class="selflink" id="section-4.11.4" href="#section-4.11.4">4.11.4</a>. Compression Algorithm Names</span>
The following table identifies the initial assignments of the
Compression Algorithm names.
Compression Algorithm Name Reference
-------------------------- ---------
none [SSH-TRANS, <a href="#section-6.2">Section 6.2</a>]
zlib [SSH-TRANS, <a href="#section-6.2">Section 6.2</a>]
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
This protocol provides a secure encrypted channel over an insecure
network.
Full security considerations for this protocol are provided in
[<a href="#ref-SSH-ARCH" title=""The Secure Shell (SSH) Protocol Architecture"">SSH-ARCH</a>].
<span class="grey">Lehtinen & Lonvick Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-SSH-ARCH">SSH-ARCH</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell
(SSH) Protocol Architecture", <a href="./rfc4251">RFC 4251</a>, January 2006.
[<a id="ref-SSH-TRANS">SSH-TRANS</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-SSH-USERAUTH">SSH-USERAUTH</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell
(SSH) Authentication Protocol", <a href="./rfc4252">RFC 4252</a>, January
2006.
[<a id="ref-SSH-CONNECT">SSH-CONNECT</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell
(SSH) Connection Protocol", <a href="./rfc4254">RFC 4254</a>, January 2006.
[<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-RFC2409">RFC2409</a>] Harkins, D. and D. Carrel, "The Internet Key Exchange
(IKE)", <a href="./rfc2409">RFC 2409</a>, November 1998.
[<a id="ref-RFC2434">RFC2434</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC</a>
<a href="./rfc2434">2434</a>, October 1998.
[<a id="ref-RFC3526">RFC3526</a>] Kivinen, T. and M. Kojo, "More Modular Exponential
(MODP) Diffie-Hellman groups for Internet Key Exchange
(IKE)", <a href="./rfc3526">RFC 3526</a>, May 2003.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC0822">RFC0822</a>] Crocker, D., "Standard for the format of ARPA Internet
text messages", STD 11, <a href="./rfc822">RFC 822</a>, August 1982.
[<a id="ref-RFC1034">RFC1034</a>] Mockapetris, P., "Domain names - concepts and
facilities", STD 13, <a href="./rfc1034">RFC 1034</a>, November 1987.
[<a id="ref-RFC2412">RFC2412</a>] Orman, H., "The OAKLEY Key Determination Protocol",
<a href="./rfc2412">RFC 2412</a>, November 1998.
[<a id="ref-FIPS-46-3">FIPS-46-3</a>] US National Institute of Standards and Technology,
"Data Encryption Standard (DES)", Federal Information
Processing Standards Publication 46-3, October 1999.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers January 2006</span>
Authors' Addresses
Sami Lehtinen
SSH Communications Security Corp
Valimotie 17
00380 Helsinki
Finland
EMail: sjl@ssh.com
Chris Lonvick (editor)
Cisco Systems, Inc.
12515 Research Blvd.
Austin 78759
USA
EMail: clonvick@cisco.com
Trademark Notice
"ssh" is a registered trademark in the United States and/or other
countries.
<span class="grey">Lehtinen & Lonvick Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc4250">RFC 4250</a> SSH Protocol Assigned Numbers 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).
Lehtinen & Lonvick Standards Track [Page 20]
</pre>
|
