What is the difference between SSH and SSL and why would we care?
SSL stands for "secure sockets layer". We care because it allows browsers to transmit information to and from a web server in a relaxed cryptographic manner to make existence tough for 1/3 birthday party spies monitoring all net site visitors.
SSH stands for "secure shell". We care as it allows a networked computer 1 to offer to get admission to a shell on networked pc 2. The user may have a degree of self-belief that spies paying attention to the insecure channel can't decrypt facts sent among the networked computers.
SSL and SSH each should do with supplying a gadget to encrypt and decrypt records over an insecure channel.
When a browser visits a URL that begins with "https://", the browser speaks HTTP over an SSL connection.
SSL enabled internet servers (as an example apache HTTP server) may be configured to apply SSL to emerge as an "secure web server". A website served up with the aid of a cozy internet server will purpose customers to access the URL through the "https://" protocol as opposed to "Http://". With the https protocol, the customers will have a stage of confidence that third-celebration spies tracking the net channel will only get hold of encrypted content material.
SSL is a protocol that could be applied within the 6th layer (presentation layer) of the OSI version.
SSH has its delivery protocol independent from SSL, so that means ssh does now not use SSL under the hood.
Cryptographically, both at ease shell and cozy sockets layer are similarly relaxed.
An SSL termination proxy can manage incoming SSL connections, decrypting the SSL and passing at the unencrypted request to other servers.
SSL helps you to use a PKI (public-key infrastructure) via signed certificates. With ssh, you have to change the key fingerprints manually through another protocol like FTP or provider pigeon.
