summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorZooko <zookog@gmail.com>2016-12-26 20:06:36 +0000
committerPádraig Brady <P@draigBrady.com>2016-12-28 16:34:34 +0000
commitb02631b14b2a155c4a233c8e8dad2569c159e85d (patch)
tree2d72a06b1bfa94f49fdc73b159398b0f548dcc34 /doc
parentd1a1276979c4744587c8a81e2b212c244512e83b (diff)
downloadcoreutils-b02631b14b2a155c4a233c8e8dad2569c159e85d.tar.xz
doc: recommend b2sum as well as SHA2
b2sum is faster, easier to use safely, and more future-proof
Diffstat (limited to 'doc')
-rw-r--r--doc/coreutils.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index a507280bd..201964456 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -3819,8 +3819,9 @@ are vanishingly small. However, it should not be considered secure
against malicious tampering: although finding a file with a given MD5
fingerprint is considered infeasible at the moment, it is known how
to modify certain files, including digital certificates, so that they
-appear valid when signed with an MD5 digest.
-For more secure hashes, consider using SHA-2. @xref{sha2 utilities}.
+appear valid when signed with an MD5 digest. For more secure hashes,
+consider using SHA-2, or the newer @command{b2sum} command.
+@xref{sha2 utilities}. @xref{b2sum invocation}.
If a @var{file} is specified as @samp{-} or if no files are given
@command{md5sum} computes the checksum for the standard input.