5 | | == What is GPG? == |
| 5 | == GnuPG, gpg, OpenPGP, PGP, what does it all mean? == |
| 6 | |
| 7 | There are a lot of confusing acronyms involved in email encryption. Here's a very brief explanation: |
| 8 | |
| 9 | GnuPG (also known as GPG) stands for Gnu Privacy Guard ([http://gnu.org Gnu] is a project to create an entirely free operating system). |
| 10 | |
| 11 | [http://gnupg.org GnuPG] is an implementation of the open standard called [http://openpgp OpenPGP]. An open standard means that a group of people have come together to decide on how to communicate. The OpenPGP folks have defined a way to communicate encrypted information securely. GnuPG is one program (of many) that uses this standard. GnuPG is free software and is one of the most popular implementations of OpenPGP. |
| 12 | |
| 13 | == In plain language, what does it mean to encrypt my email? == |
| 14 | |
| 15 | For most of us, when we first decide we want to encrypt our email, we only think about one half of the equation: scrambling our message in a way that only the intended recipient can read it. |
| 16 | |
| 17 | A second, and equally important component that is often over looked is authenticity. If someone sends you a secret message, how do you know it was sent by the person who is claiming to have sent it? |
| 18 | |
| 19 | Encryption (scrambling your message) and authenticity (knowing who really sent the message) are the two pillars of secure communication. You must have both to securely send private messages between two parties. |
| 20 | |
| 21 | Therefore, when sending mail using GnuPG, you will typically want to both encrypt the message ''and'' digitally sign the message. When receiving email using GnuPG you will typically want to de-crypt the message ''and'' verify the signature. |
| 22 | |
| 23 | == Public and private keys == |
| 24 | |
| 25 | The technology behind encryption relies on keys. Keys are nothing more than a small text file with a lot of random-seeming characters in them. [http://current.workingdirectory.net/pages/identity/ My gpg key] can serve as an example for the curious. In order to use OpenPGP you will need to generate a public/private key pair. That means you will need to keys: one that is public and one that is private. These two keys are generated together because they have a special relationship: |
| 26 | |
| 27 | * A message encrypted with the public key can only be de-crypted with the private key |
| 28 | * A message signed with the private key can be validated with the public key |
| 29 | |
| 30 | As the names imply, the private key should be kept private. You should never, under any circumstances, share this key with anybody else. The public key, on the other hand, should be freely given to everyone. |
| 31 | |
| 32 | If someone has your public key, then they will be able to send you an encrypted message ''and'' if you send them a signed message, they will be able to verify your signature. |
| 33 | |
| 34 | It's important to note: you cannot send someone an encrypted message unless you ''already'' have their public key. In other words, it is not enough that ''you'' know how to use OpenPGP, your intended recipient must also know how to use, have it setup on their computer, already have a public key, and already have given you their public key. Similarly, you cannot verify someone's signature unless you already have the sender's public key. |