security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-21 10:09:57 +01:00
Code Activity

doc: Explain that qualified.txt is a legacy method.

Browse Source 
--
This commit is contained in:
Werner Koch 2024-11-22 13:44:43 +01:00
parent 261a08566e
commit f0bca16ad3
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/gpgsm.texi
View File

@ -966,16 +966,20 @@ like this:
@item qualified.txt
@efindex qualified.txt
This is the list of root certificates used for qualified certificates.
They are defined as certificates capable of creating legally binding
signatures in the same way as handwritten signatures are. Comments
start with a hash mark and empty lines are ignored. Lines do have a
length limit but this is not a serious limitation as the format of the
entries is fixed and checked by @command{gpgsm}: A non-comment line starts with
optional whitespace, followed by exactly 40 hex characters, white space
and a lowercased 2 letter country code. Additional data delimited with
by a white space is current ignored but might late be used for other
purposes.
This is the legacy method to mark root certificates as usable for
qualified certificates. Qualified certificates are capable of
creating legally binding signatures in the same way as handwritten
signatures. The modern method to mark such root certificates is to
use the "qual" flag in the system trustlist.txt; see the gpg-agent man
page for details.
Comments int his file start with a hash mark and empty lines are
ignored. Lines do have a length limit but this is not a serious
limitation as the format of the entries is fixed and checked by
@command{gpgsm}: A non-comment line starts with optional whitespace,
followed by exactly 40 hex characters, white space and a lowercased 2
letter country code. Additional data delimited with by a white space
is current ignored but might late be used for other purposes.
Note that even if a certificate is listed in this file, this does not
mean that the certificate is trusted; in general the certificates listed