I had never seen a much simpler explanation of encryptions. Thanks. One more thing, at 16.39 Bob (in yellow) should have shared his public key, and not private key, mostly.
Hello, it would be very helpful to be providing links to the docs and/or material where we would possibly learn more.. Thank you for the awesome content!!
Based on how PKI encryption works, D is definitely the wrong answer, because it is suggesting encryption using a private key - a blatantly wrong statement. I think Google made a typo here. They should have public in place of private.
Hello your channel is very helpful. The d answer is tricky since it llok like the client side is encrypting the message with is private key which will make the message unreadable. Google cloud question should be more clear and not confusing or maybe I'm wrong
@@AwesomeGCP Yes but in PKI the private key is for decryption not encryption, if you encrypt with your private key, then who can decrypt your message ? Normally you encrypt with the public key of who's the message is for.
If you and I were communicating, you'd encrypt the message you send to me with my public key and I'd decrypt it with my private key. To send you a message, I encrypt it with your public key, which only you can decrypt with your private key.
@@AwesomeGCP your explanation is correct. Yes, encryption is always done with public key (on the sender side) and decryption is always done with private key (on the recipient side). However the option D suggesting to encrypt the message on the client side (sender side) using the originating private key. So, either the Option D has a typo "private" instead of public.. and if it is not a typo, then the option D would not work. In that case, the most probable answer would be option C.
This one is still tripping me up, should it not be C? D seems incorrect due the fact that encryption should be through a public key, not a private key - cloud.google.com/kms/docs/asymmetric-encryption - " The sender retrieves the recipient's public key. The sender uses the public key to encrypt plaintext. The sender sends the ciphertext to the recipient. The recipient uses the recipient's private key to decrypt the ciphertext. The recipient can now view the plaintext. "
In the case of C, only one of them has a private key - typically used by a client-server communication. In D, both have their own, separate private keys, which is more suitable for chat where the two participants are equal.
I had never seen a much simpler explanation of encryptions. Thanks. One more thing, at 16.39 Bob (in yellow) should have shared his public key, and not private key, mostly.
Oops, my mistake. The diagram is ok but I said it wrong. Bob should be sharing his public key.
very important question and concept. good work!
I love your explanations my friend, thank you.
Best explanation of SSL and PKI!
Hello, it would be very helpful to be providing links to the docs and/or material where we would possibly learn more..
Thank you for the awesome content!!
Wonderful explanation! Thanks.
Based on how PKI encryption works, D is definitely the wrong answer, because it is suggesting encryption using a private key - a blatantly wrong statement. I think Google made a typo here. They should have public in place of private.
Hello your channel is very helpful.
The d answer is tricky since it llok like the client side is encrypting the message with is private key which will make the message unreadable. Google cloud question should be more clear and not confusing or maybe I'm wrong
In a chat, both sides are both clients and servers. So both have their own private key and public key. The question is tough, but it looks fine to me.
@@AwesomeGCP Yes but in PKI the private key is for decryption not encryption, if you encrypt with your private key, then who can decrypt your message ? Normally you encrypt with the public key of who's the message is for.
If you and I were communicating, you'd encrypt the message you send to me with my public key and I'd decrypt it with my private key. To send you a message, I encrypt it with your public key, which only you can decrypt with your private key.
@@AwesomeGCP your explanation is correct. Yes, encryption is always done with public key (on the sender side) and decryption is always done with private key (on the recipient side).
However the option D suggesting to encrypt the message on the client side (sender side) using the originating private key.
So, either the Option D has a typo "private" instead of public.. and if it is not a typo, then the option D would not work.
In that case, the most probable answer would be option C.
This one is still tripping me up, should it not be C? D seems incorrect due the fact that encryption should be through a public key, not a private key - cloud.google.com/kms/docs/asymmetric-encryption -
"
The sender retrieves the recipient's public key.
The sender uses the public key to encrypt plaintext.
The sender sends the ciphertext to the recipient.
The recipient uses the recipient's private key to decrypt the ciphertext. The recipient can now view the plaintext.
"
In the case of C, only one of them has a private key - typically used by a client-server communication. In D, both have their own, separate private keys, which is more suitable for chat where the two participants are equal.