Explain the reason:
SSL, namely Secure Sockets Layer, is a security protocol proposed by Netscape Company when it launched the first version of Web browser.
SSH, also known as secure shell, was formulated by IETF's network working group, which is a relatively reliable protocol at present, providing security for remote login sessions and other network services.
SSL is as fair as a Certificate Authority (CA) and can determine the identity of the sender. Song Seung Heon, on the other hand, may be attacked in the middle, which is equivalent to modern eavesdropping. If an attacker is inserted between a user and a remote host (for example, in a public ***wifi area), a forged public key is used to obtain the user's login password. Then log in to the remote host with this password, and the security mechanism of SSH will be gone. However, most man-in-the-middle attacks can be avoided by ensuring that the insecure SSL/TLS protocol is disabled and the URL you visit starts with HTTPS. The SSL termination agent can process incoming SSL connections, decrypt SSL and pass unencrypted requests to other servers. SSL allows you to use PKI (Public Key Infrastructure) by signing certificates. With SSH, you must manually exchange key fingerprints through other protocols such as ftp.
SSH has a user authentication layer, SSL does not (but because it does not need authentication function). When UTF-8 encoding is used, SSH protocol uses more protocols. Considering that there are more potential attacks, SSH seems to have a larger attack surface. But this is only because SSH has a complete application built in. Security is almost the same as SSL.
Conceptually, we can use SSH and replace the tunnel part with the tunnel part in SSL, or even use HTTPS and SSH with data transmission to replace SSL transactions, and use hooks to extract the server public key from the certificate. There is no scientific impossibility. If they are operated properly, their safety will remain unchanged.