aboutsummaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2017-08-04 14:39:31 +1200
committerTom Ryder <tom@sanctum.geek.nz>2017-08-04 14:39:51 +1200
commit61438a453b5cd7c13c2deadf937816448bf34d7a (patch)
tree047be6d6738ca414a2b8c87094936f1e002a880f /README.markdown
parentAdjust compatibility notes (diff)
downloadcheckem-61438a453b5cd7c13c2deadf937816448bf34d7a.tar.gz
checkem-61438a453b5cd7c13c2deadf937816448bf34d7a.zip
Correct and link SHA1 note
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown11
1 files changed, 6 insertions, 5 deletions
diff --git a/README.markdown b/README.markdown
index fcd98ff..8aaeb3d 100644
--- a/README.markdown
+++ b/README.markdown
@@ -43,8 +43,8 @@ Run it on a fast disk, mostly. For large directories or large files, it will
probably be I/O bound in most circumstances.
If you end up hashing a lot of files because their sizes are the same, and
-you're not worried about SHA256 technically being broken in practice, SHA1 is a
-tiny bit faster:
+you're not worried about [SHA-1 technically being broken in practice][1], it's
+a tiny bit faster:
$ CHECKEM_ALG=sha1 checkem /dir
@@ -61,7 +61,8 @@ it in as optional behaviour.
License
-------
-Copyright (c) [Tom Ryder][1]. Distributed under an [MIT License][2].
+Copyright (c) [Tom Ryder][2]. Distributed under an [MIT License][3].
-[1]: https://sanctum.geek.nz/
-[2]: https://www.opensource.org/licenses/MIT
+[1]: https://shattered.io/
+[2]: https://sanctum.geek.nz/
+[3]: https://www.opensource.org/licenses/MIT