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


Ignore:
Timestamp:
Aug 28, 2012, 8:54:45 AM (8 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • openpgp/software/gpg

    v4 v5  
    131131 * Publish the key directly:
    132132  * First, lookup the key id:
    133   {{{
    134         gpg --list-key ross@ross.mayfirst.org
    135   }}}
     133{{{
     134pg --list-key jamie@mayfirst.org
     135}}}
    136136  * Next, send the key, referencing the key id:
    137   {{{
    138   gpg --send-key EEC168BA
    139   }}}
     137{{{
     138gpg --send-key EEC168BA
     139}}}
    140140
    141141This 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.
     
    145145 * Email the signature (and entire key) to the recient
    146146  * First, export the key to a text file:
    147   {{{
    148   gpg --export --armour ross@ross.mayfirst.org > ross.asc
    149   }}}
    150         * Next, send ross.asc as an attachment to the key owner.
     147{{{
     148gpg --export --armour jamie@mayfirst.org > jamie.asc
     149}}}
     150  * Next, send jamie.asc as an attachment to the key owner.
    151151
    152152There is still a small risk with this method - since the recipient may get a validly signed key that they could accidentally publish.