Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Signed keys procedure?



On Thu, 2006-09-21 at 23:50 -0400, David Kramer wrote:
> Bill Horne wrote:
> 
> > Last, encrypt the exported key and send it to the keyowner:
> > 
> > $ gpg -e -r <key id of recipient> -o <fname>.txt <fname>.asc
> > 
> > ... and then attach <fname>.txt to an email and send it to the key
> > owner.
> 
> Should that have an -a ?
> 

David,

Yes, it should. 

I left it off because I have the "armor" option set in
~/.gnupg/gpg.conf. Since I've never had the need to generate a
non-ASCII-armored file, I use it as the default.

I also have the default_key option set, since I use only one key.

Here's my gpg.conf file:

        no-greeting
        local-user 27A2880C
        default-key 27A2880C
        armor
        no-escape-from-lines
        keyserver hkp://subkeys.pgp.net
        keyserver-options auto-key-retrieve no-include-revoked

HTH.

Bill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.blu.org/pipermail/discuss/attachments/20060922/a7c9267a/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org