Secsh Workgroup RFCs

Browse Secsh Workgroup RFCs by Number

RFC4250 - The Secure Shell (SSH) Protocol Assigned Numbers: 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. [STANDARDS-TRACK]
RFC4251 - The Secure Shell (SSH) Protocol Architecture: The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK]
RFC4252 - The Secure Shell (SSH) Authentication Protocol: The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK]
RFC4253 - The Secure Shell (SSH) Transport Layer Protocol: The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.; This document describes the SSH transport layer protocol, which typically runs on top of TCP/IP. The protocol can be used as a basis for a number of secure network services. It provides strong encryption, server authentication, and integrity protection. It may also provide compression.; Key exchange method, public key algorithm, symmetric encryption algorithm, message authentication algorithm, and hash algorithm are all negotiated.; This document also describes the Diffie-Hellman key exchange method and the minimal set of algorithms that are needed to implement the SSH transport layer protocol. [STANDARDS-TRACK]
RFC4254 - The Secure Shell (SSH) Connection Protocol: Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.; This document describes the SSH Connection Protocol. It provides interactive login sessions, remote execution of commands, forwarded TCP/IP connections, and forwarded X11 connections. All of these channels are multiplexed into a single encrypted tunnel.; The SSH Connection Protocol has been designed to run on top of the SSH transport layer and user authentication protocols. [STANDARDS-TRACK]
RFC4255 - Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints: This document describes a method of verifying Secure Shell (SSH) host keys using Domain Name System Security (DNSSEC). The document defines a new DNS resource record that contains a standard SSH key fingerprint. [STANDARDS-TRACK]
RFC4256 - Generic Message Exchange Authentication for the Secure Shell Protocol (SSH): The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes a general purpose authentication method for the SSH protocol, suitable for interactive authentications where the authentication data should be entered via a keyboard (or equivalent alphanumeric input device). The major goal of this method is to allow the SSH client to support a whole class of authentication mechanism(s) without knowing the specifics of the actual authentication mechanism(s). [STANDARDS-TRACK]
RFC4335 - The Secure Shell (SSH) Session Channel Break Extension: The Session Channel Break Extension provides a means to send a BREAK signal over a Secure Shell (SSH) terminal session. [STANDARDS-TRACK]
RFC4344 - The Secure Shell (SSH) Transport Layer Encryption Modes: Researchers have discovered that the authenticated encryption portion of the current SSH Transport Protocol is vulnerable to several attacks.; This document describes new symmetric encryption methods for the Secure Shell (SSH) Transport Protocol and gives specific recommendations on how frequently SSH implementations should rekey. [STANDARDS-TRACK]
RFC4419 - Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol: This memo describes a new key exchange method for the Secure Shell (SSH) protocol. It allows the SSH server to propose new groups on which to perform the Diffie-Hellman key exchange to the client. The proposed groups need not be fixed and can change with time. [STANDARDS-TRACK]
RFC4462 - Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol: The Secure Shell protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network.; The Generic Security Service Application Program Interface (GSS-API) provides security services to callers in a mechanism-independent fashion.; This memo describes methods for using the GSS-API for authentication and key exchange in SSH. It defines an SSH user authentication method that uses a specified GSS-API mechanism to authenticate a user, and a family of SSH key exchange methods that use GSS-API to authenticate a Diffie-Hellman key exchange.; This memo also defines a new host public key algorithm that can be used when no operations are needed using a host's public key, and a new user authentication method that allows an authorization name to be used in conjunction with any authentication that has already occurred as a side-effect of GSS-API-based key exchange. [STANDARDS-TRACK]
RFC4716 - The Secure Shell (SSH) Public Key File Format: This document formally documents an existing public key file format in use for exchanging public keys between different Secure Shell (SSH) implementations.; In addition, this document defines a standard textual representation for SSH public key fingerprints. This memo provides information for the Internet community.
RFC4819 - Secure Shell Public Key Subsystem: Secure Shell defines a user authentication mechanism that is based on public keys, but does not define any mechanism for key distribution. No common key management solution exists in current implementations. This document describes a protocol that can be used to configure public keys in an implementation-independent fashion, allowing client software to take on the burden of this configuration.; The Public Key Subsystem provides a server-independent mechanism for clients to add public keys, remove public keys, and list the current public keys known by the server. Rights to manage public keys are specific and limited to the authenticated user.; A public key may also be associated with various restrictions, including a mandatory command or subsystem. [STANDARDS-TRACK]