1.4.3 // proper syntax for --edit-key cross-certify ?

vedaal at hush.com vedaal at hush.com
Thu Apr 6 19:05:59 CEST 2006

David Shaw dshaw at jabberwocky.com wrote on
Thu Apr 6 18:09:20 CEST 2006:

> default-key !keyid

doesn't work, ;-((
(does it need any additional input? ) 

here is the command line output (using cygwin):

with the existing option of

default-key 0x5AA20C866A589A97

$ gpg --clearsign c:/r/1234.txt
gpg: using subkey 04ADEE20 instead of primary key 6A589A97

You need a passphrase to unlock the secret key for
user: "vedaal nistar (preferred e-mail address) <vedaal at hush.com>"
gpg: using subkey 04ADEE20 instead of primary key 6A589A97
4096-bit RSA key, ID 04ADEE20, created 2001-04-26 (main key ID 

Enter passphrase:

now with the option of
default-key !0x5AA20C866A589A97

$ gpg --clearsign c:/r/1234.txt
gpg: no default secret key: secret key not available
gpg: c:/r/1234.txt: clearsign failed: secret key not available

putting the ! in front of the keyid 
caused an inability to identify the key,
rather than parsing the '!' 
as an option for the default keyid of 0x5AA20C866A589A97

what did you to to get it to work on your system?
(i didn't try it with the short [8 character keyid] in gpg.conf )


Concerned about your privacy? Instantly send FREE secure email, no account required

Get the best prices on SSL certificates from Hushmail

More information about the Gnupg-users mailing list