Changes between Version 4 and Version 5 of openpgp/software/gpg

Timestamp:

Aug 28, 2012, 12:54:45 PM (13 years ago)

Author:

Jamie McClelland

Comment:

--

openpgp/software/gpg

@@ -131 +131 @@
  * Publish the key directly:
   * First, lookup the key id:
-  {{{
-        gpg --list-key ross@ross.mayfirst.org
-  }}}
+{{{
+pg --list-key jamie@mayfirst.org
+}}}
   * Next, send the key, referencing the key id:
-  {{{
-  gpg --send-key EEC168BA
-  }}}
+{{{
+gpg --send-key EEC168BA
+}}}
 
 This method has a draw back. If you are not certain that the owner of the key really does control the email address of the User ID that you just signed, you could be tricked into signing (and publishing publicly) and false key.
@@ -145 +145 @@
  * Email the signature (and entire key) to the recient
   * First, export the key to a text file:
-  {{{
-  gpg --export --armour ross@ross.mayfirst.org > ross.asc
-  }}}
-        * Next, send ross.asc as an attachment to the key owner.
+{{{
+gpg --export --armour jamie@mayfirst.org > jamie.asc
+}}}
+  * Next, send jamie.asc as an attachment to the key owner.
 
 There is still a small risk with this method - since the recipient may get a validly signed key that they could accidentally publish.