HTTPS and confirmation public key private key understanding

1, the sender private key encryption, the recipient public key decryption. The information received by the recipient can be shown to originate from the true sender.

2. The sender is encrypted with the public key, and the receiver decrypts it with the private key. As long as the private key is not compromised, the information sent is guaranteed to be secure.

3, CA Certificate Center, because the recipient receives the public key may be false public key, this will lead to the receiver receives the information is not really from the bearer who holds the real private key.

Therefore, the third-party certificate structure is introduced, the digital certificate is produced by encrypting the sender's public key with the third-party certificate authority's private key, and then the recipient receives the digital certificate and decrypts the digital certificate with the public key of the certificate authority.

Gets the public key to the sender, and then uses the public key to verify that the received data is from the true sender.

4, digital certificate, the third-party certificate authority with the private key to the sender's public key to encrypt the information

5, the certificate signature, the digital certificate signature, to differentiate the certificate structure to issue the different digital certificate?? I don't know, either.

Resources:

1. What is http://www.ruanyifeng.com/blog/2011/08/what_is_a_digital_signature.html digital signature?

2, https://showme.codes/2017-02-20/understand-https/Perhaps, it is easier to understand HTTPS

HTTPS and confirmation public key private key understanding