signature problem using Ägypten in kmail
Ingo Klöcker
kloecker@kde.org
Tue Aug 19 23:06:02 2003
--Boundary-02=_aFpQ/j0lr6MzEqV
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Tuesday 19 August 2003 21:41, David Shaw wrote:
> On Tue, Aug 19, 2003 at 09:27:45PM +0200, Ingo Kl=F6cker wrote:
> > On Tuesday 19 August 2003 20:56, Bernhard Reiter wrote:
> > > Can't say for sure,
> > > but this is likely to be a bug related to the KMail frontend
> > > and not the crypto backend.
> > >
> > > Can you send an example of such an email
> > > and point to the necessary public key?
> > > Without such an example it is not possible
> > > to try and recreate that problem.
> >
> > http://bugs.kde.org/show_bug.cgi?id=3D62501
> >
> > In short: He was using GnuPG 1.2.2. After updating to GnuPG 1.3.2
> > the problems went away.
>
> 1.3.2 or 1.2.3 ?
>
> I want to get 1.3.x transformed into 1.4 at some point....
Hmm, now I'm confused. At least I used all versions of GnuPG up to=20
post-1.2.3rc1 without problems with KMail. I didn't try the 1.3.x=20
development versions.
k b (whom you forgot to cc) will have to answer which version he used to=20
fix his problem.
Regards,
Ingo
--Boundary-02=_aFpQ/j0lr6MzEqV
Content-Type: application/pgp-signature
Content-Description: signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)
iD8DBQA/QpFaGnR+RTDgudgRAm9YAKDOLw75tM4s7m8561/ZCPPt+105jgCgvZwa
vOnUTFrgsabOaIYalTnbcr8=
=c0gg
-----END PGP SIGNATURE-----
--Boundary-02=_aFpQ/j0lr6MzEqV--