security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

doc: Add comments on the legacy status of gpgconf.conf.

Browse source 
--
This commit is contained in:
Werner Koch 2022-01-25 10:06:30 +01:00
parent 9f64bf6c0b
commit b64cae5abb
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
2 changed files with 19 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
doc/tools.texi
View file

@ -298,6 +298,8 @@ shall go into the respective configuration file.
@item --apply-defaults
Update all configuration files with values taken from the global
configuration file (usually @file{/etc/gnupg/gpgconf.conf}).
Note: This is a legacy mechanism. Please use global configuraion
files instead.
@item --list-dirs [@var{names}]
@itemx -L
@ -952,8 +954,12 @@ effect.
@node Listing global options
@subsection Listing global options
Sometimes it is useful for applications to look at the global options
file @file{gpgconf.conf}.
Some legacy applications look at the global configuration file for the
gpgconf tool itself; this is the file @file{gpgconf.conf}. Modern
applications should not use it but use per component global
configuration files which are more flexible than the
@file{gpgconf.conf}. Using both files is not suggested.
The colon separated listing format is record oriented and uses the first
field to identify the record type:
@ -1094,8 +1100,10 @@ More fields may be added in future to the output.
@item /etc/gnupg/gpgconf.conf
@cindex gpgconf.conf
If this file exists, it is processed as a global configuration file.
A commented example can be found in the @file{examples} directory of
the distribution.
This is a legacy mechanism which should not be used tigether with
the modern global per component configuration files. A commented
example can be found in the @file{examples} directory of the
distribution.
@item @var{GNUPGHOME}/swdb.lst
@cindex swdb.lst
@ -1134,6 +1142,9 @@ More fields may be added in future to the output.
@end ifset
@mansect description
This is a legacy script. Modern application should use the per
component global configuration files under @file{/etc/gnupg/}.
This script is a wrapper around @command{gpgconf} to run it with the
command @code{--apply-defaults} for all real users with an existing
GnuPG home directory. Admins might want to use this script to update he