[pkg-gnupg-maint] GnuPG package split and interlocking dependencies
Yuri D'Elia
wavexx at thregr.org
Fri Oct 13 09:38:59 UTC 2017
Sorry for the late reply, this skipped far in my backlog :/
On Tue, Sep 12 2017, Werner Koch wrote:
> I can imagine use cases were you do not want any network access. Thus
> dirmngr could be a (strongly) recommended package. It might be that
> this triggers some bugs but not installing dirmngr is a good way to
> avoid all accidental network access.
I currently have no-autostart and disable-dirmngr since it became
available in gpg.conf to enforce this.
> I have no opinion on whether scdaemon should be installed by default.
I'll always favor smaller packages, so I'm biased here. I'm using gpg in
batch mode most of the time, and in servers or VMs scdaemon is useless.
As I stated before, I really don't want automatic spawning of processes
or network access by default in scripts, thus I also don't need dirmngr
there.
But I already said that, so I guess I don't have much to add :/
More information about the pkg-gnupg-maint
mailing list