PGP/GnuPG in 1.60
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi friends, the plugin for PGP 6.5.8 works well here. With GnuPG however, there are some problems. TB! lets me sign messages with GPG, but it refuses to encrypt or decrypt, the error msg telling me that the key was not found (although it is in my keyring). I can encrypt to myself, though. GPGShell de- or encrypts without problems. Anything on my side that I can do? - -- Cheers Peter * This message was created using The Bat!, version 1.60, under Windows 98, 4, 10, build , on a Pentium II machine at 200MHz, 64 MB RAM :-) . -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) Comment: GnuPG-signed for better authentication. :-) iD8DBQE8n3W1AzZSBuEHdM4RAsyvAKDRmSvYPLRNpwnE3IIoGCYZ3RUqsgCcDToE LQ6eXx/96lPUauTr6RmlUk0= =Rsrl -END PGP SIGNATURE- _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
Re: PGP/GnuPG in 1.60
My experience is that one is better off using GnuPG through the GPGshell tray program than with The Bat's plug-in. Reliability is better and the options are greater. I found some of TB's menu options didn't produce with GnuPG, including poor key management. The tray options do not produce exta work, just extra control. -- JN Peter Meyns wrote on Monday, March 25, 2002: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi friends, the plugin for PGP 6.5.8 works well here. With GnuPG however, there are some problems. TB! lets me sign messages with GPG, but it refuses to encrypt or decrypt, the error msg telling me that the key was not found (although it is in my keyring). I can encrypt to myself, though. GPGShell de- or encrypts without problems. Anything on my side that I can do? _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
Re: PGP/GnuPG in 1.60
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 25 Mar 2002 13:21:41 -0600GMT (which was 25.03.02, 20:21 +0100GMT where I live), Joseph N. wrote this about PGP/GnuPG in 1.60: JN My experience is that one is better off using GnuPG through the JN GPGshell tray program than with The Bat's plug-in. Reliability is JN better and the options are greater. I found some of TB's menu options JN didn't produce with GnuPG, including poor key management. The tray JN options do not produce exta work, just extra control. Thank you Joseph, if I consider this, you are perfectly right. I don't need any plugins when the tool itself works properly... :o)) - -- Cheers Peter Winamp currently playing: - silence - -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) - GPGshell v2.25 Comment: GnuPG-signed for better authentication. :-) Comment: Key-ID: 0xE10774CE iD8DBQE8n32YAzZSBuEHdM4RAtDEAKCBMx4ZW2Y78wyx4GY0jMJF2w5v2wCdHO7X Sb4Zq7yxGmqgEOzSEfHm7ds= =zV+n -END PGP SIGNATURE- _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
Re: PGP/GnuPG in 1.60
Hello Peter Meyns, On Monday, March 25 2002 at 11:09 AM PDT, you wrote: the plugin for PGP 6.5.8 works well here. With GnuPG however, there are some problems. TB! lets me sign messages with GPG, but it refuses to encrypt or decrypt, the error msg telling me that the key was not found (although it is in my keyring). I can encrypt to myself, though. TB did have a problem with something called 'Smart Matching' where it would look in your Key Rings for a User ID with the 'exact' matching UID of the Recipient... or something along those lines, and in most cases would provide the Key with the 'first' matching UID it came across, regardless whether or not this was the Key you wanted to use. However, you mention that you can encrypt and decrypt messages to yourself without a problem, so this may not be the case. Perhaps TB looks up the 'exact' matching UID of 'any' Public Keys you are encrypting to and compares it with the UID of the Recipient, and if it doesn't find an exact match, will report that the Key cannot be found? -- Nick Andriash Courtenay, B.C. Canada _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
Re: PGP/GnuPG in 1.60
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @ 20:09:02 +0100 [ Mon, 25 Mar 2002], Peter Meyns [PM] contributed this to our collective wisdom: ... PM the plugin for PGP 6.5.8 works well here. With GnuPG however, there PM are some problems. TB! lets me sign messages with GPG, but it PM refuses to encrypt or decrypt, the error msg telling me that the key PM was not found (although it is in my keyring). I can encrypt to PM myself, though. GPGShell de- or encrypts without problems. PM Anything on my side that I can do? TB!'s plug-in has smart-matching hard coded into how it works. What this means is that for signing, it will only do so if it finds on your keyring, a key with an associated UID that perfectly matches the From: address in the message headers. When I say perfect match, I mean name and e-mail address *together*. For instance, if your keys UID is 'Jasper Jones [EMAIL PROTECTED]', TB!'s plugin will not sign if you fill in your messages 'from:' address as 'Jasper [EMAIL PROTECTED]'. You have to add the latter identity as another UID. This is why I have a list of UID's on my main key: Allie [EMAIL PROTECTED] Allie C Martin [EMAIL PROTECTED] Allie C Martin [EMAIL PROTECTED] Allie Martin [EMAIL PROTECTED] Allie Martin [EMAIL PROTECTED] Allie Martin [EMAIL PROTECTED] Allie Martin [EMAIL PROTECTED] The advantage of this system applies when you have multiple keys. With this smartmatching system, the plug-in will autosign with the appropriate key instead of a default key as in PGP. I have an alternate key for this list with the UID 'allie_M [EMAIL PROTECTED]'. Signing of messages to this list is template driven and the correct key to sign with is always appropriately chosen. The encryption/decryption of messages follows a similar system. An UID match must occur before the encryption decryption process is done. Otherwise you'll receive an error message. A typical example is that you're replying to a message from someone who's public key doesn't include their reply to name/address combo as a UID. I don't see any advantages of including smart-matching in encryption/decryption operations. Let the user select the relevant keys. If it's the correct key then the person at the other end will be able to decrypt it. If you choose the wrong key to decrypt with, then the message will not decrypt. Simple. I don't know what's with the smart matching and I tend to just use GPG Shell for this. However, I find the plugin very nice for signing and signature checking once you are aware of how it works and add your identities, which you should anyway. - -- Allie C Martin (_ List Moderator and fellow end user __) PGPKey - mailto:[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-= TB! v1.60 Windows XP 5.1.2600 ¯¯ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6-2 (MingW32) iEYEARECAAYFAjyfiCcACgkQV8nrYCsHF+KavQCgrUwZUoRRXPAiUQk161Ihgda2 fTgAoNK6lliW5M3xRdROGZSgnXLIUJ3A =uKf4 -END PGP SIGNATURE- _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
Re: PGP/GnuPG in 1.60
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @ 13:21:41 -0600 [ Mon, 25 Mar 2002], Joseph N. [JN] thoughtfully wrote the following: ... JN My experience is that one is better off using GnuPG through the JN GPGshell tray program than with The Bat's plug-in. Reliability is JN better and the options are greater. The possibilities are greater if you use both together, taking advantage of each of their strengths. In this way, I actually much prefer using GPG to PGP at present. My only problem is the key auto-retrieval problem that GPG has when run on NT-based systems. JN I found some of TB's menu options didn't produce with GnuPG, Yes. The plugin isn't that developed to include these components and I suspect this is so because the existence of GPG Shell is known. :-) JN including poor key management. You can't manage keys via the TB! plugin. You have to use the GPG CLI. JN The tray options do not produce exta work, just extra control. Well, mostly yes. However, if you're in the habit of signing a lot of messages in a predictable fashion, nothing beats setting this up to be automated and forgetting about it, especially if you use multiple keys. GPG Shell doesn't offer this automation, but TB!'s plugin does. :-) - -- Allie C Martin -- List Moderator PGPKey - mailto:[EMAIL PROTECTED] [MUA: TB! v1.60 (*) OS: Windows XP 5.1.2600] _ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6-2 (MingW32) iEYEARECAAYFAjyfid4ACgkQV8nrYCsHF+LpLgCfU5rFRl83EvlYDXXtZUdWGEyV TEgAoLwCG7axj9IgEUJNGe0BGYuNw2gw =h2Fz -END PGP SIGNATURE- _ Archives : http://tbbeta.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Bugs/Wishes: https://bt.ritlabs.com/
