Secure Shell: Difference between revisions
Jump to navigation
Jump to search
imported>Sandy Harris No edit summary |
imported>David Finn No edit summary |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{subpages}} | |||
The '''Secure Shell''' or '''SSH''' is a network protocol for secure remote login, providing an encrypted connection instead of the unencrypted, and therefore insecure, connection of [[telnet]]. | The '''Secure Shell''' or '''SSH''' is a network protocol for secure remote login, providing an encrypted connection instead of the unencrypted, and therefore insecure, connection of [[telnet]]. | ||
The protocol is documented in a series of RFCs. <ref>{{citation | There was an [http://www.ietf.org/wg/concluded/secsh.html IETF Working Group] for SSH; it has completed its work. The protocol is documented in a series of RFCs. <ref>{{citation | ||
| id = rfc4251 | | id = rfc4251 | ||
| author = S. Lehtinen, C. Lonvick | |||
| title = The Secure Shell (SSH) Protocol Assigned Numbers | |||
| date = January 2006 | |||
| url = http://www.ietf.org/rfc/rfc4251.txt | |||
}}</ref> <ref>{{citation | |||
| id = rfc4250 | |||
| author = T. Ylonen, C. Lonvick | | author = T. Ylonen, C. Lonvick | ||
| title = The Secure Shell (SSH) Protocol Architecture | | title = The Secure Shell (SSH) Protocol Architecture | ||
| date = January 2006 | | date = January 2006 | ||
| url = http://www.ietf.org/rfc/ | | url = http://www.ietf.org/rfc/rfc4250.txt | ||
}}</ref> <ref>{{citation | }}</ref> <ref>{{citation | ||
| id = rfc4252 | | id = rfc4252 | ||
| Line 31: | Line 38: | ||
| date = January 2006 | | date = January 2006 | ||
| url = http://www.ietf.org/rfc/rfc4255.txt | | url = http://www.ietf.org/rfc/rfc4255.txt | ||
}}</ref> <ref>{{citation | |||
| id = rfc4256 | |||
| author = F. Cusack, M. Forssen | |||
| title = Generic Message Exchange Authentication for the Secure Shell Protocol (SSH) | |||
| date = January 2006 | |||
| url = http://www.ietf.org/rfc/rfc4256.txt | |||
}}</ref> <ref>{{citation | }}</ref> <ref>{{citation | ||
| id = rfc4716 | | id = rfc4716 | ||
| Line 39: | Line 52: | ||
}}</ref> | }}</ref> | ||
Most Unix-based systems include an SSH client, and often a server as well. A client for Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]. | Most Unix-based systems include an SSH client, and often a server as well. The [http://www.openssh.com/ Open SSH] project, part of [[OpenBSD]], are the main developers. A client for Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]. | ||
== References == | == References == | ||
{{reflist}} | {{reflist}} | ||
Latest revision as of 12:22, 22 November 2011
The Secure Shell or SSH is a network protocol for secure remote login, providing an encrypted connection instead of the unencrypted, and therefore insecure, connection of telnet.
There was an IETF Working Group for SSH; it has completed its work. The protocol is documented in a series of RFCs. [1] [2] [3] [4] [5] [6] [7] [8]
Most Unix-based systems include an SSH client, and often a server as well. The Open SSH project, part of OpenBSD, are the main developers. A client for Windows is Putty.
References
- ↑ S. Lehtinen, C. Lonvick (January 2006), The Secure Shell (SSH) Protocol Assigned Numbers, rfc4251
- ↑ T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Protocol Architecture, rfc4250
- ↑ T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Authentication Protocol, rfc4252
- ↑ T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Transport Layer Protocol, rfc4253
- ↑ T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Connection Protocol, rfc4254
- ↑ J. Schlyter, W. Griffin (January 2006), Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints, rfc4255
- ↑ F. Cusack, M. Forssen (January 2006), Generic Message Exchange Authentication for the Secure Shell Protocol (SSH), rfc4256
- ↑ J. Galbraith, R. Thayer (November 2006), The Secure Shell (SSH) Public Key File Format, rfc4716