Differences between version 4 and previous revision of PublicKeyEncryption.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, March 10, 2004 3:50:25 am | by StuartYeates | Revert |
| Older page: | version 3 | Last edited on Tuesday, February 17, 2004 5:43:41 pm | by AristotlePagaltzis | Revert |
@@ -11,14 +11,14 @@
# PKE is computationally difficult to decode.
# PKE does not require a secure channel to send the key; the key is, in fact, public.
# PKE can be used as a basis of a personal (digital) signature so that the sender may always be identified.
-If you encrypt something with the public key then it can be only decrypted with the private key, and vice versa. Given the public key, you can't deduce the private key, and __usually__ vice versa (although not always). Thus you publish you public key to the world, and everyone can send you encrypted email. (See [PGP
]).
+If you encrypt something with the public key then it can be only decrypted with the private key, and vice versa. Given the public key, you can't deduce the private key, and __usually__ vice versa (although not always). Thus you publish you public key to the world, and everyone can send you encrypted email. (See [GPG
]).
You can "sign" a document by taking a CryptographicHash of the document, and encrypting that with your private key. Everyone can calculate the hash, and then decrypt the version you gave and verify that they are the same (the document hasn't been modified) and they know that it came from you (since you are the only one that has your private key).
-You can then sign other peoples' key to say that you verify that it is them. This
is known as the
WebOfTrust.
+You can then sign other peoples' key to say that you verify that it is them. A collection of such signatures
is called a
WebOfTrust.
See also PublicKeyAuthentication.
----
Part of CategorySecurity
