[[CRC32]], is not a cryptographiclycryptographically secure hash function. It is easy to intentionally create a file with a given CRC32 checksum. The fact that a file's checksum corresponds with the checksum in the SFV file is therefore no guarentee that the file has not been tampered with. However, SFV is well suited to detect 'random' changes.
a file's checksum corresponds with the checksum in the SFV file is therefore no guarentee, that the file has not been tampered with. However SFV is well suited to detect 'random' changes.
Other hash functions, such as [[SHA512]], are better suited for ensuring the authenticity of files. But this is only helpfull, if there a secure second channel to get the checksums. ▼
▲Other hash functions, such as [[SHA512]], are better suited for ensuring the authenticity of files. But this is only helpfull,helpful if there is a secure second channel to get the checksums.
