diff options
| author | Norbert Preining <preining@logic.at> | 2016-04-12 06:07:29 +0000 |
|---|---|---|
| committer | Norbert Preining <preining@logic.at> | 2016-04-12 06:07:29 +0000 |
| commit | e4ea0d46df62e587ae70e6ab7711ac1c013bef32 (patch) | |
| tree | 84b438cd8e72aaef828f435736014d05d613b751 | |
| parent | 07df4636752b37d5a7b0ae410986dcb96a815e4e (diff) | |
adjust security document according to kb suggestions
git-svn-id: svn://tug.org/texlive/trunk@40428 c570f23f-e606-0410-a88d-b1316a301751
| -rw-r--r-- | Master/tlpkg/doc/tl-security-proposal.txt | 28 |
1 files changed, 6 insertions, 22 deletions
diff --git a/Master/tlpkg/doc/tl-security-proposal.txt b/Master/tlpkg/doc/tl-security-proposal.txt index 87c9296cc24..83f9b3210da 100644 --- a/Master/tlpkg/doc/tl-security-proposal.txt +++ b/Master/tlpkg/doc/tl-security-proposal.txt @@ -1,6 +1,6 @@ Security Proposal for TeX Live ============================== -(last change NP 2016-01-03) +(last change NP 2016-01-04) We use md5 sums in the following places: 1) md5sum of the texlive.tlpdb in texlive.tlpdb.md5 in tlnet/tlcritical @@ -38,25 +38,9 @@ There is no need to sign each container, as we are having indirectly signed sha256 hashes of the containers (in the tlpdb, which is sha256-ed, and then signed). - -Transition notes: -* I would like to have a start on this already *before* - 2016, but during 2015 we would have: - - if gpg is not available, or remote .sha256.gpg is not - available, silently continue (same behaviour as now) - After 2016 I suggest that if either of the above two - fail (gpg not available, or remote .sha256.gpg not - found), then tlmgr stops - unless --no-verification is - passed in or set in the tlmgr configuration file. -* At least till after 2016 is released we need to generate - both texlvie.tlpdb.md5 and .sha256 on the remote server, - otherwise updates from versions before cannot verify - (hmm, maybe they can - as we do not break if there is - no md5 sum available - so maybe this is not necessary - at all and we can simply switch without any problem!) -* gpg binaries: - for windows I guess we have to ship it, for all others - we should be able to assume that it is there. Those - who do not have access to gpg need to set --no-verification - in the configuration file. +Usage: +* if gpg is found, try to use it, otherwise just + give warning about how to verify/gpg necessary +* only if gpg is available, download .sha256.asc and + verify |