RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 4254, "The Secure Shell (SSH) Connection Protocol", January 2006

Note: This RFC has been updated by RFC 8308

Source of RFC: secsh (sec)
See Also: RFC 4254 w/ inline errata

Errata ID: 6850
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Hamid Nazari
Date Reported: 2022-02-14
Verifier Name: Paul Wouters
Date Verified: 2023-07-28

Section 5.1 says:

Requests for assignments of new SSH_MSG_CHANNEL_OPEN 'reason code'
values (and associated 'description' text) in the range of 0x00000005
to 0xFDFFFFFF MUST be done through the IETF CONSENSUS method, as
described in [RFC2434].  The IANA will not assign Channel Connection
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 [RFC2434].


It should say:

Requests for assignments of new SSH_MSG_CHANNEL_OPEN_FAILURE 'reason code'
values (and associated 'description' text) in the range of 0x00000005
to 0xFDFFFFFF MUST be done through the IETF CONSENSUS method, as
described in [RFC2434].  The IANA will not assign Channel Connection
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 [RFC2434].

Notes:

The 'reason code' is present on SSH_MSG_CHANNEL_OPEN_FAILURE message to denote cause of the failure while original text attributes it to SSH_MSG_CHANNEL_OPEN by mistake.

Report New Errata



Advanced Search