-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ***^\ ."_)~~ ~( __ _"o Was another beautiful day, Sun, 15 Oct 2006, @ @ at 07:14:35 +0500, when Richard H. Stoddard wrote:
> 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? Richard, whatever might be the case, and your DSA key certainly is not the reason, you should anyway make a new -- but an RSA -- key, of at least some honest 3072 bits, since DSA keys are not safe as they were once (upon a time) and hence should be gradually withdrawn from (active) cryptographic life. On how to make easily and quickly such a key (using GnuPG) you have instructions here, if you need them: <http://blueness.port5.com/gpg/>, "2. How to make a key in GnuPG using command line". Since these instructions are based on mainly default values, if you want to enable the "Authenticate" function, just toggle the "A" value, when these values are offered. * As for the inconsistent work of the crypto "band" the members of are here TBat, WinPT and GnuPG, I suspect that WinPT is the one that is causing it. Its author also himself hints (on the other list) that it is the possible reason, due to certain incompleteness of this software. Try GPGShell instead and I think you'll not have such problems anymore. * As for The Bat, in this, crypto, regard, it also is not quite "complete", despite its very good (one of the best) integration with GnuPG, and although it makes no problem in this particular case you describe it should be "corrected" at least as for the list of keys it offers, the list that is "filtered" after the addresses of particular account and thus very annoyingly limited. _All_ the user's keys being on his key-ring(s) should appear and be at disposal on such a list, regardless whether the addresses in key IDs correspond to the actual account we work at the moment or not, or whether these IDs have some email address at all or not. The ways user uses his/her crypto software must not be limited in any way, particularly not by a "third" applications, like mailers are and similar (since they have absolutely nothing with the ways crypto strategies are applied and _must not_ interfere and tinker with it) and the said conception is long since outdated, very limited and rigid, being thus not very merrily functional. To the correction like this should be given highest priority, after the level of its essential importance of course, not after "popularity" some "wish" is rated, that is after the number of members who "vote" some less or more idio...matic (and often quite redundant) "feature" for. This is the reason why I myself do not take part in any "whish list" creation, since such conception (based on the numbers and not on the essential sense) makes no any functional and serious sense and is thus pretty much useless and resource wasting. - -- Mica ~~~ For personal mail please use my address as it is *exactly* given in my "From" field, otherwise it will not reach me. ~~~ GPG keys/docs/software at: http://blueness.port5.com/pgpkeys/ http://tronogi.tripod.com/pgp/pgpkeys/ [Earth LOG: 670 day(s) since v3.0 unleashing] OSs: Windows 98 SE Micro Lite Professional IVa Enterprise Millennium Windows XP(ee) Micro Lite Professional 1.6, Gentoo & Vector ~ Wine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6-svn-4217 <>o<> tiger192 i686 (MSYS/MinGW32) iQEVAwUBRTOQmrSpHvHEUtv8AQiqRAf/RruYXW8+UwvkdchTaTSwbAr5wQ3JeAQH j8BnvOD603+8jygL2U1yiathSv0llQTLo7pyDKiD1aOrqPzpTzjSJC0RyrFCyUQ7 uTJVdl1KVcQSN+wQ23iD3fN91IjHf5lGrDicgTUHk4dgttVBD/6XC38MAyOV4Eje FO0UQlWJCw4K4jaegwlDKHXWQowjV31fpcs7KvtadkkV5tqRn9KHECbLxPCM3QR2 RPPwFez602Owkx8HbzrW1h3ZyMOW7gWHTop0/3oo8WnWHgXfZc6smk7vMju5E86a 7oW9bGLpwBSB09+zpf7TZd7EOjgfl2PTj0IwrWxmxk09Icm2CnZbEQ== =uCdV -----END PGP SIGNATURE----- ________________________________________________ Current version is 3.85.03 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
