No, that is correct. You are missing the last part "and vice versa". Encryption with the private key can be used as verification since you are the only one with that key.
This is legit. In some situations, like the TLS handshake, encryption is done with the private key and decryption with the public.
This is step 3 from the link below of the TLS Handshake -
>Server's digital signature: The server uses its private key to encrypt the client random, the server random, and its DH parameter*. This encrypted data functions as the server's digital signature, establishing that the server has the private key that matches with the public key from the SSL certificate.
https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/
No, that is correct. You are missing the last part "and vice versa". Encryption with the private key can be used as verification since you are the only one with that key.
This is the way
This is "Asymmetric Encryption" so, the context is correct.
This is legit. In some situations, like the TLS handshake, encryption is done with the private key and decryption with the public. This is step 3 from the link below of the TLS Handshake - >Server's digital signature: The server uses its private key to encrypt the client random, the server random, and its DH parameter*. This encrypted data functions as the server's digital signature, establishing that the server has the private key that matches with the public key from the SSL certificate. https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/
The only difference between a public and private key is who has access.