prokop/thgtoa
1
0
Fork 0
mirror of https://github.com/Anon-Planet/thgtoa.git synced 2026-03-25 06:03:27 +01:00
Code Issues Packages Projects Releases Wiki Activity

Finished an incomplete sentence

Browse Source
This commit is contained in:
Alex Anderson
2022-05-18 00:18:04 +00:00
parent 82a93e4864
commit daeef609c1
118 changed files with 787 additions and 785 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide.md
View File

@@ -10451,7 +10451,7 @@ This is because they do not prevent Collision[^478] well enough and could allow
For this reason, it is usually recommended to use SHA-based[^479] hashes and the most used is probably the SHA-2[^480] based SHA-256 for verifying file integrity. SHA is much more resistant to collisions[^481] than CRC and MD5. And collisions with SHA-256 or SHA-512 are rare and hard to compute for an adversary.
If a SHA-256 checksum is available from the source of the file, you should not hesitate to use it to confirm the integrity of the file. *Note: SHA-1 *
If a SHA-256 checksum is available from the source of the file, you should not hesitate to use it to confirm the integrity of the file. *Note: SHA-1 is not recommended.*
This checksum should itself be authenticated/trusted and should be available from an authenticated/trusted source (obviously you should not trust a file just because it has a checksum attached to it alone).