-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
On Wed, 02 Mar 2005 14:40:13 -0500 (2:40 PM here), David Calvarese
[DC] wrote in mid:[EMAIL PROTECTED]:
gpg: conversion from `utf-8' to `CP0' not available
DC Upgrade to the 1.4.1rc2, it fixes that problem.
This does resolve the
Kevin Coates wrote:
Hi David,
On Wed, 02 Mar 2005 14:40:13 -0500 (2:40 PM here), David Calvarese
[DC] wrote in mid:[EMAIL PROTECTED]:
gpg: conversion from `utf-8' to `CP0' not available
DC Upgrade to the 1.4.1rc2, it fixes that problem.
This does resolve the problem.
DC Note that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
on Thu, 03 Mar 2005 11:21:24 -0500GMT, you wrote:
[encrypting to multiple keys]
This is more of a function of GPG. Basically you need to create a
group entry in your gpg.conf file with the e-mail address of PGPNET
followed by the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
***^\ ._)~~
~( __ _o Was another beautiful day, Wed, 02 Mar 2005,
@ @ at 19:25:18 -0500, when David Calvarese wrote:
gpg: WARNING: signature digest conflict in message
gpg: BAD signature from David Calvarese
And for this
Hi,
I'm having problems with both GnuPG and PGP with regards to
integration with TB! The problems are more severe with GnuPG, so I'll
start with that. Please note that I'm still using TB! v2.12.00. I'm
using GnuPG v1.4.0, and PGP v8.1.
Here's what happens when I try to verify a simple inline
Melissa Reese wrote:
Here's what happens when I try to verify a simple inline clear
signature using the TB! integration with GnuPG:
gpg: conversion from `utf-8' to `CP0' not available
Upgrade to the 1.4.1rc2, it fixes that problem.
Note that there are other GnuPG issues, especially when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
***^\ ._)~~
~( __ _o Was another beautiful day, Wed, 02 Mar 2005,
@ @ at 14:40:13 -0500, when David Calvarese wrote:
.
I get this when check your signature, David. This sort of GPG message is
new to me. What that would mean?
Mica Mijatovic wrote:
***^\ ._)~~
~( __ _o Was another beautiful day, Wed, 02 Mar 2005,
@ @ at 14:40:13 -0500, when David Calvarese wrote:
.
I get this when check your signature, David. This sort of GPG message is
new to me. What that would mean?
gpg: Signature
Hi David,
On Wednesday, March 02, 2005, at 11:40:13 AM PST, you wrote:
Upgrade to the 1.4.1rc2, it fixes that problem.
Hee hee! I just sent you an off-list message relating the interesting,
yet disturbing experience of installing this new version of GnuPG.
Problems went way beyond simple TB!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
***^\ ._)~~
~( __ _o Was another beautiful day, Wed, 02 Mar 2005,
@ @ at 15:06:24 -0500, when David Calvarese wrote:
Mica Mijatovic wrote:
I get this when check your signature, David. This sort of GPG message is
new to me. What
Mica Mijatovic wrote:
I'm not sure, but do you have my keys in your keyring? If that's not
it, maybe someone on the list will know.
I got your keys and it shows this:
gpg: Signature made 03/02/05 20:40:16 Central Europe Standard Time using DSA
key ID 1C9D5360
gpg: WARNING: signature
-BEGIN PGP SIGNED MESSAGE-
Hi
On Thursday 3 March 2005 at 12:25:18 AM, in
mid:[EMAIL PROTECTED], David Calvarese wrote:
I'm not sure either... They're showing good sigs on my end when I
look in my sent items folder. Maybe because I'm using something
other than SHA-1 as a digest...
Hi MFPA,
On Wednesday, March 02, 2005, at 4:43:42 PM PST, you wrote:
I cannot verify Melissa's messages because I don't have the keys
Did you see the URL in my signature? :-)
but the rest of this thread all check out OK here, using PGP8.1
By the way, the message of David's that Mica found
-BEGIN PGP SIGNED MESSAGE-
Hi
On Thursday 3 March 2005 at 1:03:13 AM, in
mid:[EMAIL PROTECTED], Melissa Reese wrote:
I cannot verify Melissa's messages because I don't have the keys
Did you see the URL in my signature? :-)
I forgot to look there. After PGP tried some keyservers and
14 matches
Mail list logo
