Or just go ahead and try it. Start your free 30 days of evaluation today and download
ZOC Terminal V7.15.4 now.
(The program offers easy and complete
uninstall in case you are not convinced
by the trial.)
What is a Secure Shell Client?
When you're working with client/server computing, a general terminal or a terminal
emulator is used to send and receive data from the host. Because of this, the terminal
or the PC that is running a terminal emulator
needs to somehow be connected to the server or mainframe computer.
There are several different methods that can be used to connect the two, but in the past, the most commonly used method of connecting a terminal to a server over a network was Telnet.
Unencrypted transmission via Telnet today presents a serious security risk, because anybody on the network with some knowledge and tools can monitor the data exchange - even down to details like usernames, passwords.
Because of the ever-increasing demand for security, the Secure Shell (SSH) protocol was developed. SSH uses advanced encryption technology to encrypt every single piece of communication between the client (called secure shell client) and the server. Should an unauthorized third party be able to intercept traffic somewhere along the communication path, they will see nothing but completely useless data.
Secure Shell Client Features and Requirements
There are many benefits to using a secure shell client. On top of the encryption of
the data transfer and secure key exchange, the SSH protocol also offers verification
that you are connected to the correct computer.
This may seem surprising, but it makes perfect sense. Keep in mind that if somebody were able to control any part of the communication path, they could actually reroute the traffic to another computer. This can then play the role of the computer which you actually wanted to connect to, and could either display fake data or obtain information from the client computer - both of which could be equally damaging. When you use a secure shell client, you don't need to worry about these kinds of scenarios.
A SSH client should also support different authentication methods. These include username/password, public/private key, and various custom formats. The latter might include a system where the server could obtain information that only the authorized users know, e.g. by using a hardware ID card or by sending an access code to the user's mobile phone.
A good secure shell client needs to be able to connect to various different servers. In order to do this, it has to support latest key exchange and encryption protocols, because what seemed unbreakable five years ago, is considered less so today. If the server switches to more advanced encryption methods, ssh clients need to support these as well.
Other typical must have features for a ssh client would be:
Technical SSH Essentials
The basis of the SSH protocol are laid out in IETF internet standard RTF 4253.
The document describes SSH as a secure transport that provides cryptographic
host, strong encryption, authentication, and integrity protection.
Or, as RFC 4253 states in its own words:
The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.It hence defines ways to create a shared encryption key in the possible presence of a listener, host and user authentication methods (i.e. ways in which users and server can prove that they are who they claim to be), and possible data compression to more effectively transmit data.
[...] The protocol can be used as a basis for a number of secure network services. It provides strong encryption, server authentication, and integrity protection. It may also provide compression.
Key exchange method, public key algorithm, symmetric encryption algorithm, message authentication algorithm, and hash algorithm are all negotiated.
An especially challenging part of encrypting communication over public networs, is the need to negotiation a shared secret (an encryptino key) over a channel that might already be monitored by an adversary.
SSH answers this challenge through the initial key exchange phase of the connection using the older Diffie-Hellman kex method. Never versions now also support ED25519 elliptic curve kex. It is a specific implementation of the Edwards-curve Digital Signature Algorithm (EdDSA), which itself is a variant of Schnorr's signature system with Twisted Edwards curves (math heavy details can be found in the upcoming IETF standard for ED25519.
Good Terminal Emulator based on the SSH Protocol
However, SSH only covers the actual transmission of data between the
client and server. But the SSH client
is usually a terminal emulator,
i.e. a software that allows a remote computer to receive keyboard input
from, and send formatted text (color, cursor placement, etc.)
to the user's computer.
Obviously, the client still needs to be able to perform the functions of a terminal - supporting various terminal emulations, printing, logging, and so on. This is why ZOC is the ideal Secure Shell Client, it does all of the above, and more.
ZOC Terminal Download
Read more about our secure shell client ZOC,
check its feature list,
look at our screenshots or
start your free 30 days of evaluation today and
ZOC Terminal V7.15.4