Mica, Monday, October 16, 2006, 7:01:06 PM, you wrote:
MM> Richard, whatever might be the case, and your DSA key certainly is not MM> the reason, you should anyway make a new -- but an RSA -- key, of at MM> least some honest 3072 bits, since DSA keys are not safe as they were MM> once (upon a time) and hence should be gradually withdrawn from (active) MM> cryptographic life. I was going to do that one of these days anyway. With WinPT, I have the option of creating an RSA key up to 4096; with PGP I can create an RSA key only up to 2048, while a DH/DSS key can go to 4096. Which is the better option for PGP? (Eventually I will phase out of using PGP, but need to have GnuGP working reliably first.) Also, how do I change the hash algorithm? With PGP v8.1 I have several algorithm options, but they all seem to result in a hash SHA1. MM> As for the inconsistent work of the crypto "band" the members of are MM> here TBat, WinPT and GnuPG, I suspect that WinPT is the one that is MM> causing it. Its author also himself hints (on the other list) that it is MM> the possible reason, due to certain incompleteness of this software. Try MM> GPGShell instead and I think you'll not have such problems anymore. I think I've identified my problem. Yesterday I used only PGP and it worked just fine, both encrypting and decrypting. Tonight it started out okay, but then I started WinPT to check it out, and now PGP claims it can't copy text from the window. Seems there's a conflict when both are running. The obvious solution, of course, is to use only one of them at a time. MM> As for The Bat, in this, crypto, regard, it also is not quite MM> "complete", despite its very good (one of the best) integration with MM> GnuPG, and although it makes no problem in this particular case you MM> describe it should be "corrected" at least as for the list of keys it MM> offers, the list that is "filtered" after the addresses of particular MM> account and thus very annoyingly limited. _All_ the user's keys being on MM> his key-ring(s) should appear and be at disposal on such a list, MM> regardless whether the addresses in key IDs correspond to the actual MM> account we work at the moment or not, or whether these IDs have some MM> email address at all or not. I'm still having some problems with TB!'s integration. For example, I seem to be able to decrypt okay - most of the time - but tonight it still tells me there is no secret key when I try to sign/encrypt using its privacy menu options. WinPT, on the other hand, was working tonight, although now I'm having troubles again. (It keeps defaulting to another open message to sign, and after closing that one it now tells me there it could not extract text from the window.) Again, maybe if I use just one of them I'll be okay. Thanks for all of the advice and assistance. -- Rick ________________________________________________ Current version is 3.85.03 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
