Editing 1553: Public Key

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 11: Line 11:
  
 
Since the public key is initially designated to be shared, anyone who has that key can send the user an encrypted message that only the user can decrypt. [[Cueball]] has been following this rule, but he notices that it appears nobody has ever used his public key for anything. He contemplates sharing his ''private'' key, which he believes would generate more interest in him personally. However, he appears to overlook the fact that doing so would allow anyone to decrypt messages sent to him, thus defeating the entire purpose of encryption. (Although some systems can confirm the message sender by having a secret encryption key and a public decryption one, though this is negated again if both keys are released.)
 
Since the public key is initially designated to be shared, anyone who has that key can send the user an encrypted message that only the user can decrypt. [[Cueball]] has been following this rule, but he notices that it appears nobody has ever used his public key for anything. He contemplates sharing his ''private'' key, which he believes would generate more interest in him personally. However, he appears to overlook the fact that doing so would allow anyone to decrypt messages sent to him, thus defeating the entire purpose of encryption. (Although some systems can confirm the message sender by having a secret encryption key and a public decryption one, though this is negated again if both keys are released.)
 +
 +
If Cueball had initially released his private key instead of his public one, it would make no difference, since the importance is in keeping one key private - the keys themselves do not hold "private" or "public" roles until one is released and becomes the public key. However, since Cueball has already released his public key, releasing his private key would compromise the key pair. Even if he attempted to remove records of his public key, chances are that some sites would still have it somewhere.
  
 
The title text refers to another feature of Public-key cryptography: In addition to assuring that certain messages can only be read by a specific key owner, it can also assure that certain messages could only have been ''written'' by a specific key owner, by "signing" it using the private key. Anyone can read a signed message, but readers with the public key can then verify that the owner of the private key wrote (or at least signed) the message, rather than someone pretending to be the owner. If Cueball published his private key, then anybody could sign any message as him, effectively impersonating him and also defeating the purpose of encryption.
 
The title text refers to another feature of Public-key cryptography: In addition to assuring that certain messages can only be read by a specific key owner, it can also assure that certain messages could only have been ''written'' by a specific key owner, by "signing" it using the private key. Anyone can read a signed message, but readers with the public key can then verify that the owner of the private key wrote (or at least signed) the message, rather than someone pretending to be the owner. If Cueball published his private key, then anybody could sign any message as him, effectively impersonating him and also defeating the purpose of encryption.

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)