[Pkg-gnupg-maint] Why 2.1 is delayed for so long
eric at debian.org
Sun Sep 21 03:09:53 CEST 2014
* Werner Koch (wk at gnupg.org) wrote:
> > So i think that gpg2.1 needs to somehow detect that the running agent is
> > old, and either fail more gracefully (making it clear to the user or
> > actually restart the agent if it can be sure that gpg-agent is the right
> > version.
> Restarting without user consent might be problematic.
My $0.02 is that it's fine to just print an error with instructions on
how to restart your gpg-agent.
> > 0) dirmngr
> > gpg2.1 depends on the latest version of dirmngr for any/all of its
> > remote access functionality (e.g. keyserver fetches). Debian has
> > traditionally packaged dirmngr separately from gnupg, but it looks like
> > we should really bring the two of them together. This is is
> > debian-specific packaging work; we've already gotten permission of the
> > dirmngr maintainer to do this, so it's just outstanding work that needs
> The question is whether the old dirmnagr is at all useful. How many are
> using it to check CRLs or run OCSP checks for X.509?
Does the new version not support the same operations as the old one?
> Or would it be useful to rename the new dirmngr so that both can
> co-exist? The name is anyway alien to GnuPG.
Eric Dorland <eric at kuroneko.ca>
43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: Digital signature
More information about the Gnupg-devel