Hi, all:
I provide an RPM package called gnupg22-static for those who need to run
newer versions of GnuPG on CentOS-7 environments (it's stuck on
gnupg-2.0 there). For compilation, I use the convenient STATIC=1
mechanism, but there's still the problem that all paths end up being
hardcoded to
Hello,
I just saw the following bug reported in Arch Linux repos:
https://bugs.archlinux.org/task/63147
with the title "[gnupg] 2.2.17 release is broken by design and breaks
pacman".
It appears Arch's packages use Web of Trust for introducing new
developers by adding 3 signatures out of 5 (o
Am Freitag, 12. Juli 2019, 10:30:30 CEST schrieb Werner Koch via Gnupg-users:
> On Wed, 10 Jul 2019 21:47, johan...@zarl-zierl.at said:
> > ...except it isn't installed by default. Will this be part of
> > gpg-wks-client?
> Ooops. I meant gpg-wks-client. There is no gpg-wks-tool.
Thanks for the
On Wed, 10 Jul 2019 21:47, johan...@zarl-zierl.at said:
> ...except it isn't installed by default. Will this be part of gpg-wks-client?
Ooops. I meant gpg-wks-client. There is no gpg-wks-tool.
> won't be installed to libexec), it would still be beneficial to describe the
> actual file system
