diff options
author | Norbert Preining <preining@logic.at> | 2018-04-01 00:49:11 +0000 |
---|---|---|
committer | Norbert Preining <preining@logic.at> | 2018-04-01 00:49:11 +0000 |
commit | 41943477ecd818eb82a094bce321ea21f7ed8237 (patch) | |
tree | 52bfdeee162492d0f51ef709221c7324c2ce67e9 /Master | |
parent | 9da8f04dabdeec25b5d75b677ddc6d393a4a9d06 (diff) |
update docs on new crypto option
git-svn-id: svn://tug.org/texlive/trunk@47211 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master')
-rwxr-xr-x | Master/texmf-dist/scripts/texlive/tlmgr.pl | 23 |
1 files changed, 11 insertions, 12 deletions
diff --git a/Master/texmf-dist/scripts/texlive/tlmgr.pl b/Master/texmf-dist/scripts/texlive/tlmgr.pl index 0e944e8dd77..657a32f5cbf 100755 --- a/Master/texmf-dist/scripts/texlive/tlmgr.pl +++ b/Master/texmf-dist/scripts/texlive/tlmgr.pl @@ -9075,18 +9075,17 @@ main repository be signed, but not any additional repositories. If C<gpg> is not available, signatures are not checked and no verification is carried out, but C<tlmgr> proceeds normally. -The verification can be controlled by the c - - -TODO TODO - -The attempted verification can be suppressed entirely by specifying -C<--verify-repos=none> on the command line, or a line -C<verify-repos = none> in a C<tlmgr> config file (see L<CONFIGURATION -FILE FOR TLMGR>). On the other hand, you can I<require> successful -verification of all repos by specifying C<--require-verification> on the command -line, or C<require-verification=1> in a C<tlmgr> config file; in this -case, if verification is not possible, or fails, the program quits. +The behaviour of the verification can be controlled by the command line +and config file option C<verify-repos> which takes one of the following +values: C<none>, C<main>, or C<all>. In case of C<none>, no verification +whatsoever is attempted, similar to the case when not GnuPG can be found. +In case of C<main> (the default) verification is required only for +the main repository, but attempted for all. Missing signatures of +subsidiary repositories will not result in an error. +Finally, in the case of C<all>, all repositories need to be signed. + +In all cases when a signature is checked and fails to verify, an error +is raised. Cryptographic verification requires checksum checking (described just above) to succeed, and a working GnuPG (C<gpg>) program (see below for |