From ba439b387a18825664241655dd8a6829cca54cf3 Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Thu, 9 Aug 2012 20:52:35 +0300 Subject: [PATCH] GPG guide: mention -a & fix typo & fix group line. --- articles/guides/GPG/GPG.html | 19 ++++++------------- articles/guides/GPG/GPG.html.md | 9 +++++---- 2 files changed, 11 insertions(+), 17 deletions(-) diff --git a/articles/guides/GPG/GPG.html b/articles/guides/GPG/GPG.html index 758d568..353cefa 100644 --- a/articles/guides/GPG/GPG.html +++ b/articles/guides/GPG/GPG.html @@ -120,6 +120,10 @@ encrypt-to KEYID

charset UTF-8

So UTF-8 is used as default character set and most of characters can be used.

+
+

armor

+
+

So you don't need to specify -a to get ASCII armoured text.

keyserver hkp://pool.sks-keyservers.net
 keyserver-options auto-key-retrieve no-include-revoked verbose import-clean

So default keyserver is specified and unknown keys are always received when something what requires missing key is procressses and revoked keys aren't included in search results and verbose output is used and signatures by unknown keys are automatically removed.

@@ -127,20 +131,9 @@ keyserver-options auto-key-retrieve no-include-revoked verbose import-cleanGroup lines

Group lines are a way to write email to one recepient and have it encrypted to multiple keys automatically.

Example group line:

-

group =0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206

+

group touchlay-server@googlegroups.com=0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206

With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys.

-

NOTE: I think that group lines require email addresses to be in format

-

NOTE: KEYIDs in group line should be in format 0xLONG. If you don't use that format by default, use "gpg2 --keyid-format 0xLONG --list-keys". >

+

NOTE: KEYIDs in group line should be in format 0xLONG. If you don't use that format by default, use "gpg2 --keyid-format 0xLONG --list-keys".

See also my Enigmail instructions about group lines.

Comments

GPG can automatically add comments to signed and encrypted content. They are usually hidden by email clients, which support GPG.

diff --git a/articles/guides/GPG/GPG.html.md b/articles/guides/GPG/GPG.html.md index 39572a3..e23637b 100644 --- a/articles/guides/GPG/GPG.html.md +++ b/articles/guides/GPG/GPG.html.md @@ -184,6 +184,10 @@ After you set 0xLONG as keyid-format, keys appear like 0x4DB53CFE82A46728 instea So UTF-8 is used as default character set and most of characters can be used. +> armor + +So you don't need to specify -a to get ASCII armoured text. + ``` keyserver hkp://pool.sks-keyservers.net keyserver-options auto-key-retrieve no-include-revoked verbose import-clean @@ -201,14 +205,11 @@ Group lines are a way to write email to one recepient and have it encrypted to m Example group line: -group =0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206 +group touchlay-server@googlegroups.com=0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206 With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys. -NOTE: I think that group lines require email addresses to be in format - NOTE: KEYIDs in group line should be in format 0xLONG. If you don't use that format by default, use "gpg2 --keyid-format 0xLONG --list-keys". -> See also my [Enigmail] instructions about group lines.