[Solved] Private/Public Key Pair, I'm unsure, please help to clarify
-
I'm unsure if I understood everything correctly. Is the following correct: 1. A Text encrypted with PRIVATE_KEY can be decrypted _only_(?) with PUBLIC_KEY 2. A Text encrypted with PUBLIC_KEY can be decrypted _only_ with PRIVATE_KEY Thank you very much for help and sorry if the question is stupid...
It does not solve my Problem, but it answers my question
-
I'm unsure if I understood everything correctly. Is the following correct: 1. A Text encrypted with PRIVATE_KEY can be decrypted _only_(?) with PUBLIC_KEY 2. A Text encrypted with PUBLIC_KEY can be decrypted _only_ with PRIVATE_KEY Thank you very much for help and sorry if the question is stupid...
It does not solve my Problem, but it answers my question
Yes, those two statements are correct.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Yes, those two statements are correct.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I'm unsure if I understood everything correctly. Is the following correct: 1. A Text encrypted with PRIVATE_KEY can be decrypted _only_(?) with PUBLIC_KEY 2. A Text encrypted with PUBLIC_KEY can be decrypted _only_ with PRIVATE_KEY Thank you very much for help and sorry if the question is stupid...
It does not solve my Problem, but it answers my question
Close. Depending on your use case, you will have a PUBLIC ENCRYPT and a PUBLIC DECRYPT key. These are completely separate key sets that are associated with PRIVATE DECRYPT and PRIVATE ENCRYPT keys respectively. Generally, you encrypt a hash with your PRIVATE ENCRYPT key to provide a digital signature, as it can be verified using your PUBLIC DECRYPT key. For actual message encryption, your PUBLIC ENCRYPT key will be used to encrypt it so that only your PRIVATE DECRYPT key can decrypt it. With the PKI model, you can freely hand out your public keys (or they are stored in a central repository, such as on a domain) while your private keys needs to be properly secured to prevent compromise.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
Close. Depending on your use case, you will have a PUBLIC ENCRYPT and a PUBLIC DECRYPT key. These are completely separate key sets that are associated with PRIVATE DECRYPT and PRIVATE ENCRYPT keys respectively. Generally, you encrypt a hash with your PRIVATE ENCRYPT key to provide a digital signature, as it can be verified using your PUBLIC DECRYPT key. For actual message encryption, your PUBLIC ENCRYPT key will be used to encrypt it so that only your PRIVATE DECRYPT key can decrypt it. With the PKI model, you can freely hand out your public keys (or they are stored in a central repository, such as on a domain) while your private keys needs to be properly secured to prevent compromise.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
Hi ! The logical to remember with Public , Private Keys is about 2 crypting channels. From both sides, 2 differents Keys will operate. Like all cryptos, one can be reverse , not the other. But the A to B, B to A must transmit all datas, and verify them. Look at what can be switch : ( What is surrounding ? ) Computer A , Computer B Keys A , Key B Private function crypto Public function crypto Clock from A(all in) , Clock from B(all in) checksum A , checksum B while you ensure no errors of receiver . The work is all done. It's "pair" working.