Josefsson, Simon Tatham, Wei Dai, Denis Bider, der Mouse, and Williams, Niels Provos, Perry Metzger, Peter Gutmann, Simon Galbraith, Ken Hornstein, Markus Friedl, Martin Forssen, Nicolas Van Dyke, Jeffrey Altman, Jeffrey Hutzelman, Jon Bright, Joseph Harris, Bill Sommerfeld, Brent McClure, Niels Moller, Damien Miller,ĭerek Fawcus, Frank Cusack, Heikki Nousiainen, Jakob Schlyter, Jeff People who should be acknowledged include Mats Andersson, Ben Many people contributed to the development of this document over the This set of documents and also made very substantial contributions. Rinne, Sami Lehtinen (all of SSHĬommunications Security Corp), and Markku-Juhani O. The major original contributors of this set of documents have been: Notation from the architecture document without reference or further This document freely uses terminology and This document should be read only after reading the SSH architectureĭocument. The 'service name' for this protocol is "ssh-connection". It provides interactive login sessions, remoteĮxecution of commands, forwarded TCP/IP connections, and forwarded SSH transport layer and user authentication protocols (Īnd ). RFC 4254 SSH Connection Protocol January 2006ġ. SSH transport layer and user authentication protocols. The SSH Connection Protocol has been designed to run on top of the All of theseĬhannels are multiplexed into a single encrypted tunnel. TCP/IP connections, and forwarded X11 connections. Interactive login sessions, remote execution of commands, forwarded This document describes the SSH Connection Protocol. Secure network services over an insecure network. Secure Shell (SSH) is a protocol for secure remote login and other Distribution of this memo is unlimited.Ĭopyright (C) The Internet Society (2006). Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the The Secure Shell (SSH) Connection Protocol Request for Comments: 4254 SSH Communications Security CorpĬategory: Standards Track C. Updated by: 8308 Errata Exist Network Working Group T. RFC 4254: The Secure Shell (SSH) Connection Protocol
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |