edit key interface in GPGME

Bernhard Reiter bernhard@intevation.de
Fri Aug 2 14:38:02 2002


--GID0FwUMdk1T2AWN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 02, 2002 at 02:24:07PM +0200, Miguel Coca wrote:
> On Fri, Aug 02, 2002 at 09:26:25 +0200, Jan-Oliver Wagner wrote:
> > to my understanding, gpa 0.5.0 does not interface with the current
> > gnupg 1.0.7.
>=20
> Yes, that potentially affects, AFAIK, everything related to the --edit-key
> menu. Gpapa just prints the commands in the menu without checking for the
> response from gpg.
>=20
> > It would therefore not be wise to make a release 0.5.1 now which would
> > require an old version of gnupg.

Yes.

> To do it properly, I think it would require to duplicate the mechanism in
> gpgme. So, I think it will be best to just go ahead and do the migration.

> I will begin to work on it shortly. I think gpapa will remain in some
> places, but it will actually use gpgme for all it's operations.

Cool.
I take it that this will lead to a gpa which will=20
be compatible with gpg 1.0.7? Or do we have to wait for 1.2 to be released?

--GID0FwUMdk1T2AWN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Sn1Bh9ag3dpKERYRAtUQAKDBf0E2yTMNt9trmzl7JRAiI3Cv6ACfWDBh
Pmuy2CaVii8L6vqzY4+d0WU=
=bjVH
-----END PGP SIGNATURE-----

--GID0FwUMdk1T2AWN--