Mica, Saturday, October 14, 2006, 11:25:54 PM, you wrote:
MM> If your GnuPG otherwise works, even if just once it was working well MM> (for instance you hit Ctrl+Shift+S in TB editor and it offers the MM> "combo" with the list of your keys), then it means that it's properly MM> installed, both with the added PATH and the registry entry. It appears to be working. I've played with it some more since my earlier post, and it now decrypts and verifies signatures just fine. (Or at least those of the person with whom I've been testing it.) 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. This morning, however, I checked the properties on my key once 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? Should I just generate a new keypair and use different settings? -- Thanks, Rick ________________________________________________ Current version is 3.85.03 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
