Secure Shell
Secure Shell (SSH) is a cryptographic network protocol for secure data communication, remote command-line login, remote command execution, and other secure network services between two networked computers. It connects, via a secure channel over an insecure network, a server and a client running SSH server and SSH client programs, respectively.[1] The protocol specification distinguishes between two major versions that are referred to as SSH-1 and SSH-2. The best-known application of the protocol is for access to shell accounts on Unix-like operating systems, but it can also be used in a similar fashion for accounts on Windows. Definition[edit] SSH uses public-key cryptography to authenticate the remote computer and allow it to authenticate the user, if necessary.[1] There are several ways to use SSH; one is to use automatically generated public-private key pairs to simply encrypt a network connection, and then use password authentication to log on. Key management[edit] Usage[edit]
SSHv1 or SSHv2? What's the big deal?
Choosing the right fishing bait is always a challenge for me. Two baits may look the same, but they are as different as Popeye's chicken Vs. Mother in law's chicken. This is how it is with SSHv1 vs SSHv2. Choosing the wrong one is like sitting in all day long meeting on tax code law without doughnuts or an Internet connection. First off, let consider what SSH really does. • Provides a secure client-server protocol that encrypts data during transmission over a network. • Offers strong authentication methods to ensure that the client and server are communicating with trusted hosts. • Prevents root access, which is typical of nonsecure network applications such as Telnet and FTP. • Is transparent to end users. • Includes, in commercial versions, and free open source options. Many network admins switched over to SSHv1 instead telnet to take advantage these features. So the original code jockey (Tatu Ylönen) that wrote SSHv1 in 1995, scraped the entire protocol and started again. Jimmy Ray
Setting up a Layer 3 tunneling VPN with using OpenSSH
Posted by emeitner on Mon 2 Jul 2007 at 16:37 This article describes how to use the new tunneling features of OpenSSH V 4.3 to establish a VPN between two Debian or Debian-like systems. Note that by tunneling I am referring to layer-3 IP-in-SSH tunneling, not the TCP connection forwarding that most people refer to as tunneling. When operational this VPN will allow you to route traffic from one computer to another network via an SSH connection. This is a brief recipe rather than a "HOW-TO". It it assumed you are familiar with all of the basic concepts. Requirements Debian Etch and/or Ubuntu Edgy systemsSSH version 4.3 or higher is required on both ends of the VPN. Introduction SSH V 4.3 introduced true layer-2 and layer-3 tunneling allowing easy to configure VPNs that can be built upon existing SSH authentication mechanisms. Previously I never allowed root login via SSH to any machines because I always logged in under a personal account and then used sudo. Scenario On the Client On the server
Quora - What's the difference between VPN tunnel & a SSH tunnel?
Difference between VPN and SSH? - Super User
Related:
Related: