diff options
author | cr-marcstevens <github@marc-stevens.nl> | 2020-01-09 17:24:09 +0300 |
---|---|---|
committer | cr-marcstevens <github@marc-stevens.nl> | 2020-01-09 17:24:09 +0300 |
commit | f7b7e9323cf669a168c635a707667e31e614ef9b (patch) | |
tree | ab461dbdae456712efa7903db2a4bebdc4e46c21 | |
parent | 855827c583bc30645ba427885caa40c5b81764d2 (diff) |
Documented SHA-mbles example colliding files
-rw-r--r-- | README.md | 3 | ||||
-rw-r--r-- | test/sha-mbles-1.bin | bin | 0 -> 640 bytes | |||
-rw-r--r-- | test/sha-mbles-2.bin | bin | 0 -> 640 bytes |
3 files changed, 2 insertions, 1 deletions
@@ -44,7 +44,8 @@ make ## Command-line usage There are two programs `bin/sha1dcsum` and `bin/sha1dcsum_partialcoll`. -The first program `bin/sha1dcsum` will detect and warn for files that were generated with a cryptanalytic SHA-1 collision attack like the one documented at https://shattered.io/. +The first program `bin/sha1dcsum` will detect and warn for files that were generated with a cryptanalytic SHA-1 collision attack, +like the one documented at https://shattered.io/ as well as the later derived attack https://sha-mbles.github.io/. The second program `bin/sha1dcsum_partialcoll` will detect and warn for files that were generated with a cryptanalytic collision attack against reduced-round SHA-1 (of which there are a few examples so far). Examples: diff --git a/test/sha-mbles-1.bin b/test/sha-mbles-1.bin Binary files differnew file mode 100644 index 0000000..5a7c30e --- /dev/null +++ b/test/sha-mbles-1.bin diff --git a/test/sha-mbles-2.bin b/test/sha-mbles-2.bin Binary files differnew file mode 100644 index 0000000..fe39178 --- /dev/null +++ b/test/sha-mbles-2.bin |