Secure Shell: Difference between revisions
Jump to navigation
Jump to search
imported>Sandy Harris No edit summary |
imported>Sandy Harris No edit summary |
||
| Line 45: | Line 45: | ||
}}</ref> | }}</ref> | ||
Most Unix-based systems include an SSH client, and often a server as well. The [http://www.openssh.com/ Open SSH] project, part of [[ | 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}} | ||
Revision as of 21:28, 11 September 2010
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. [1] [2] [3] [4] [5] [6] [7]
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
- ↑ T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Protocol Architecture, rfc4251
- ↑ 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