Skip to main content

Difference between SSH and SSL

SSH vs SSL

The internet has opened a lot of doors, and windows as well. You can essentially do anything with internet nowadays. People can buy and do transactions online. You can reboot any computer system or program in your office from your personal computer. People do not even have to leave their homes anymore.
Since there are lot of open doors and windows, hackers and eavesdroppers can illegally get personal information and have access to your personal program and files. Therefore, people now demand web security. Enter SSH and SSL.
Both are public key cryptography tunneling protocols and aims to create a secure, confidential exchange of data and connection across the network particularly, the internet. The encryption technologies used by both protocols are very reliable, and it is extremely difficult or impossible for hackers to break into them.
SSH
SSH means “Secure Shell”. It has a built-in username/password authentication system to establish a connection. It uses Port 22 to perform the negotiation or authentication process for connection. Authentication of the remote system is done by the use of public-key cryptography and if necessary, it allows the remote computer to authenticate users.
More often than not, SSH uses SSL under the hood, so they are both as secure as each other. One advantage of SSH is that using key-pair authentication is actually quite easy to do, and built right into the protocol.
SSL
SSL means “Secure Sockets Layer”. Many protocols — like HTTP, SMTP, FTP, and SSH ‘“ were adjusted to include the support of SSL. The port that it typically uses to make a connection to a secure server is 443.
Basically, it works as a tier in a certain protocol to provide cryptographic and security functions.
Unlike SSH, it does not require any authentication. It is most often implemented for transmitting information such as banking, credit card, and other vital personal information to a particular server somewhere on the internet.
Businesses operating online will most likely need an SSL certificate to provide a safer web environment for their clients. It will do just that; it will secure all the transactions and exchanges between the remote computer and the business server. It just makes business sense to have an SSL certificate.
Summary:
1. Normally, SSH uses port 22 while SSL uses port 443.
2. SSL is used predominantly for securely transmitting critical information like in credit cards and banking. On the other hand, SSH is for securely executing commands across the internet.
3. SSH uses a username/password authentication system to establish a secure connection while SSL does not really bother with it.
4. SSH is more about network tunneling while SSL is more about certificates.


Read more: Difference between SSH and SSL | Difference Between http://www.differencebetween.net/technology/difference-between-ssh-and-ssl/#ixzz5v4Uv9Wmi

Comments

Post a Comment

Popular posts from this blog

Interpreting the output of lspci

On Linux, the lspci command lists all PCI devices connected to a host (a computer). Modern computers and PCI devices communicate with each other via PCI Express buses instead of the older Conventional PCI and PCI-X buses since the former buses offer many advantages such as higher throughput rates, smaller physical footprint and native hot plugging functionality. The high performance of the PCI Express bus has also led it to take over the role of other buses such as AGP ; it is also expected that SATA buses too will be replaced by PCI Express buses in the future as solid-state drives become faster and therefore demand higher throughputs from the bus they are attached to (see this article for more on this topic). As a first step, open a terminal and run lspci without any flags (note: lspci may show more information if executed with root privileges): lspci   This is the output I get on my laptop: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Co
Post a Comment
Read more

Boot process hangs at dracut: Switching root

Environment Red Hat Enterprise Linux 6 Issue When server is booting the boot process hangs at  dracut: Switching root , and never displays anything else. Raw device-mapper: ioctl: 4.33.1-ioctl (2015-8-18) initialised: xx-xxxx@redhat.com udev: starting version 147 dracut: Starting plymouth daemon dracut: rd_NO_DM: removing DM RAID activation dracut: rd_NO_MD: removing MD RAID activation scsi0 : ata_piix scsi1 : ata_piix ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc120 irq 14 ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc128 irq 15 Refined TSC clocksource calibration: 2599.999 MHz. virtio-pci 0000:00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 virtio-pci 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, high) -> IRQ 10 virtio-pci 0000:00:07.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 virtio-pci 0000:00:08.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11 input: ImExPS/2 Gener
Post a Comment
Read more

How to get the SAN environment information and statistics on AIX, HP-UX, Linux, Solaris, and Windows

How to get the SAN environment information and statistics on AIX, HP-UX, Linux, Solaris, and Windows Description NetBackup SAN Client is supported on the Linux , Solaris, Windows, HP-UX and AIX operating systems.  These environments provide the initiator device driver which can login to the SAN client media server and mount an pseudo   target device “ARCHIVE PYTHON” so that the backup or restore can be use the fiber transport (FT).  If there is an issue in the SAN environment, it is necessary to get the information/statistics from the SAN fabric for analysis.  The commands below can be used, on the respective operating system, to gather the necessary information. If the outputs show many or steadily increasing error counts, that indicates one or more issues with  the fabric  infrastructure. The issue(s) can be caused by cabling, SFP, san switch, DWDM, HBA or ISL and those components will need to be analyzed and evaluated.  Linux Get the hardware information fo
Post a Comment
Read more