GnuPG & TB!

Greetings,

I posted a version of this to the TBUDL awhile ago, and did get some
advice. However, I'm still having problems using GnuPG, and maybe it's
more appropriate here, since the problem seems, at least to me, to be
GnuPG, not TB!.

I am able to decrypt and verify signatures okay after setting GnuPG as
my default within TB!. However, when I try to sign or encrypt, it
gives the pass phrase dialog box, but then I get an error message
saying there is no default secret key. I've repeatedly checked the
preferences to make sure the paths are correct, but still can't get
over this hurdle.

I checked the properties on my key again, and this time looked more
carefully at the subkeys. The DSA subkey can sign and certify, while
the ELG-E subkey, which has a different subkey id, can encrypt. (The
default id is the DSA key number.) Neither of them have the
authenticate box checked. Is this my problem? And if so, how do I
overcome it? I've tried everything I can think of, but to no avail.
Should I just generate a new keypair and use different settings?

Thanks for any assistance you can provide.

--
Cheers,
Rick

Messages in this topic (1) Reply (via web post) | Start a new topic

.

Rick,
this is very strange. now, i cannot decrypt your
message. this is the message i get:
Error - secret key needed to decrypt message

gpg command line and output:
C:\Program Files\GNU\GnuPG\gpg.exe --charset utf8
--batch --no-tty --status-fd 2 -d --passphrase-fd 0
--no-use-agent
gpg: using character set `utf-8'
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: PGP 8.1
:marker packet:
50 47 50
:pubkey enc packet: version 3, algo 16, keyid
XXXXXXXXXXXXXXXXX
data: [2046 bits]
data: [2048 bits]
gpg: public key is XXXXXXXX
:encrypted data packet:
length: 805
mdc_method: 2
gpg: using subkey XXXXXXXX instead of primary key
XXXXXXXX
gpg: encrypted with 2048-bit ELG-E key, ID XXXXXXXX,
created 2006-04-18
"Richard H Stoddard < rstoddard%40voyager.net">rstoddardvoyager.net>&quot;
gpg: decryption failed: secret key not available

I.e. the same message you were getting when i tried to
send encrypted messages to you.

I wonder if you added subkeys before or after you sent
the key to me (first time)

Regards,
Julia
--- "Richard H. Stoddard&quot; < rstoddard%40voyager.net">rstoddardvoyager.net>
wrote:

>; Greetings,
>
> I posted a version of this to the TBUDL awhile ago,
> and did get some
> advice. However, I'm still having problems using
>; GnuPG, and maybe it's
> more appropriate here, since the problem seems, at
> least to me, to be
> GnuPG, not TB!.
>
> I am able to decrypt and verify signatures okay
> after setting GnuPG as
> my default within TB!. However, when I try to sign
> or encrypt, it
> gives the pass phrase dialog box, but then I get an
> error message
&gt; saying there is no default secret key. I've
> repeatedly checked the
> preferences to make sure the paths are correct, but
> still can't get
> over this hurdle.
&gt;
> I checked the properties on my key again, and this
> time looked more
> carefully at the subkeys. The DSA subkey can sign
> and certify, while
>; the ELG-E subkey, which has a different subkey id,
> can encrypt. (The
> default id is the DSA key number.) Neither of them
> have the
> authenticate box checked. Is this my problem? And if
> so, how do I
> overcome it? I've tried everything I can think of,
> but to no avail.
&gt; Should I just generate a new keypair and use
> different settings?
>
> Thanks for any assistance you can provide.
>
> --
> Cheers,
&gt; Rick
>
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Messages in this topic (2) Reply (via web post) | Start a new topic

.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julia,

Sunday, October 15, 2006, 3:10:02 PM, you wrote:

JD> I wonder if you added subkeys before or after you sent
JD&gt; the key to me (first time)

Sorry, no subkeys were added since then. It's gotta be something else.

- --
Rick

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRTIQTbrieAXxW2ntEQKWiwCgzzjFbaMUnLys/VlXlIIXQ091kXQAnjIO
bkmhPrvAex2XBGSjDMnfmiL2
=377f
-----END PGP SIGNATURE-----

Messages in this topic (3) Reply (via web post) | Start a new topic

.