Help, I'm confused (how to package cryptplug)

Werner Koch wk at
Mon Apr 19 14:27:04 CEST 2004

On Mon, 19 Apr 2004 13:17:34 +0200, Michael Nottebrock said:

> gpg-agent and gpgsm into the gnupg-1.9.x versions, the deprecation of
> newpg and the recent updates to libgcrypt, all those programs have
> become ever harder to sync.

Frankly, I hope that things will get better now.  newpg used to be
only a transitional package.

> Can anybody tell me what is the recommended way to provide the crypto
> plugins right now? Use the development branch of gnupg and

For the old Kmail (the one using cryptplug), you definitely need to
use gpgme-0.3.16.  This will still work with the old backend but is of
paramount importance when using the new backend.

Using the new backend is definitley the way to go. That old newpg will
not be maintained anymore.  Thus for the *backend*, use the
instructions given at  I can't speak for the
KDE part, though.

> libgcrypt-1.2.0? Are there distributions of pinentry and dirmngr

Yes please use libgcrypt 1.2 all over the palce, it is the first
stable version and thus we will take great care not to break the ABI
or API anymore.  (Using 1.1.94 is okay too if you applied the patch I
posted right after the release).

The latest dirmngr and gnupg tarballs should all work fine with
libgcrypt 1.2.  pinentry does not need libgcrypt, but you need to take
care which Qt version to use.



More information about the Gpa-dev mailing list