2.1.14 -- dropping qualified.txt and com-certs.pem
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Fri Jul 15 03:39:37 CEST 2016
hi GnuPG folks--
in 2.1.14, c19b2061274cd50838e62a2acbdc7e7d24888e7e says:
sm: Do not install cacert and other root certificates.
* doc/Makefile.am (dist_pkgdata_DATA): Move qualified.txt and
com-certs.pem to ...
With Let's Encrypt there is no more need to push CA Cert.
Signed-off-by: Werner Koch <wk at gnupg.org>
The result is that a "make install" ends up not shipping either
/usr/share/gnupg/com-certs.pem or /usr/share/gnupg/qualified.txt
The justification about Let's Encrypt covers CA Cert, but moving these
files to not be installed by "make install" seems like it also has an
effect on the STEED "nonthority" and on the list of qualified German
network authorities -- do you envision Let's Encrypt taking over both of
those roles as well? Also, should GnuPG ship the Let's Encrypt
authority's certificate instead? If not, how will users know how to
validate LE-signed sites?
Moreover, the info for gpgsm in 2.1.14 still implies that GnuPG ships
As a distributor, i'd like to ship documentation that matches what's
installed. I see four options for the debian packaging:
0) clean up the info/man pages to not claim that any of these files will
1) go ahead and keep shipping the files from the source repo (they're
still present) even though they aren't installed by "make install"
2) decide on some new CAs to trust, write our own qualified.txt file,
and install them both.
3) point to other CA lists already installed by the OS, and generate
qualified.txt from the same sort of system-level defaults (i don't
know how to do this right now)
What do you think distros should do with this situation?
Thanks for the update and the new release!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 948 bytes
Desc: not available
More information about the Gnupg-devel