From b77802eb8a19ab035fe00b60bf3a025eaa67e3e0 Mon Sep 17 00:00:00 2001 From: Andre Klapper Date: Thu, 4 Aug 2011 15:38:54 +0200 Subject: Put new user documentation in place --- help/C/mail-encryption-gpg-create-key.page | 53 ++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 help/C/mail-encryption-gpg-create-key.page (limited to 'help/C/mail-encryption-gpg-create-key.page') diff --git a/help/C/mail-encryption-gpg-create-key.page b/help/C/mail-encryption-gpg-create-key.page new file mode 100644 index 0000000000..a99004abc5 --- /dev/null +++ b/help/C/mail-encryption-gpg-create-key.page @@ -0,0 +1,53 @@ + + + + Signing or encrypting messages via GPG that you send. + + + + + + Andre Klapper + ak-47@gmx.net + + + Novell, Inc + + +

Creative Commons Share Alike 3.0

+
+ +
+ + Creating a GPG key + +These steps are very technical. For average users we nowadays recommend using the Seahorse application for managing GPG keys. + + +

Before you can get or send GPG encrypted mail, you need to generate your public and private keys with GPG.

+ +

Open a terminal window and enter gpg --gen-key.

+

Select an algorithm, then press Enter.

+

Select a key length, then press Enter.

+

Enter how long your key should be valid for.

+

Type your real name, then press Enter.

+

Type your email address, then press Enter.

+

(Optional) Type a comment, then press Enter.

+

Review your selected user ID. If it is correct, press O.

+

Type a passphrase, then press Enter.

+

Move your mouse randomly to generate the keys.

+
+ +

After the keys are generated, you can view your key information by entering gpg --list-keys. You should see something similar to this: /home/you/.gnupg/pubring.gpg ---------------------------- pub 1024D/32j38dk2 2001-06-20 you <you@example.com> sub 1024g/289sklj3 2011-06-20 [expires: 2012-11-14]

+

GPG creates one list, or keyring, for your public keys and one for your private keys. All the public keys you know are stored in the file ~/.gnupg/pubring.gpg. If you want to give other people your key, send them that file.

+

If you want, you can upload your keys to a key server:

+ +

Check your public key ID with gpg --list-keys. It is the string after 1024D on the line beginning with pub. In the example above, it is 32j38dk2.

+

Enter the command gpg --send-keys --keyserver wwwkeys.pgp.net 32j38dk2. Substitute your key ID for 32j38dk2. You need your password to do this.

+
+ +

Key servers store your public keys for you so that your friends can decrypt your messages. If you choose not to use a key server, you can manually send your public key, include it in your signature file, or put it on your own Web page. However, it is easier to publish a key once, and then let people download it from a central place when they want.

+

If you don't have a key to unlock or encrypt a message, you can set your encryption tool to look it up automatically. If it cannot find the key, an error message appears.

+ +
-- cgit v1.2.3