Secure Shell: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Sandy Harris
No edit summary
imported>Sandy Harris
No edit summary
Line 31: Line 31:
| 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

Revision as of 20:24, 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. A client for Windows is Putty.

References

  1. T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Protocol Architecture, rfc4251
  2. T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Authentication Protocol, rfc4252
  3. T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Transport Layer Protocol, rfc4253
  4. T. Ylonen, C. Lonvick (January 2006), The Secure Shell (SSH) Connection Protocol, rfc4254
  5. J. Schlyter, W. Griffin (January 2006), Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints, rfc4255
  6. F. Cusack, M. Forssen (January 2006), Generic Message Exchange Authentication for the Secure Shell Protocol (SSH), rfc4256
  7. J. Galbraith, R. Thayer (November 2006), The Secure Shell (SSH) Public Key File Format, rfc4716