diff --git a/articles/guides/GPG/GPG.html b/articles/guides/GPG/GPG.html
index f7b2b67..758d568 100644
--- a/articles/guides/GPG/GPG.html
+++ b/articles/guides/GPG/GPG.html
@@ -135,14 +135,12 @@ document.write(''+''+e+'
'+'<\/'+
=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
-- -
See also my Enigmail instructions about group lines.
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 81e0b18..39572a3 100644 --- a/articles/guides/GPG/GPG.html.md +++ b/articles/guides/GPG/GPG.html.md @@ -207,6 +207,7 @@ With that line, when recepient is touchlay-server@googlegroups.com, then emails 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". >