This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
checksums [2014/01/13 18:05] – scmfcl | checksums [2022/10/08 16:22] (current) – scmfcl | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== File Checksums ====== | ====== File Checksums ====== | ||
- | A [[wp> | + | A [[wp> |
- | verify the integrity of that data. Typically you use a program to | + | |
- | compute | + | |
- | transmitted to some other location the same checksum algorithm is used | + | |
- | to compute the checksum there. If the two checksums are the same, it | + | |
- | is unlikely that the data has been changed during transmission. | + | |
- | You can use [[wp>MD5]] or [[wp> | + | You should **use [[wp>SHA2]]** checksums, specifically sha512 (to keep things simple), **in case of submission |
- | you submit via PATS in this way. We also use it to enable you to hand | + | |
- | in a submission | + | |
- | before the deadline. For this you simply have to send the checksum to | + | |
- | use before the submission deadline. Read the [[Submission Guide]] | + | |
- | details. | + | |
- | Below you find instructions of how to generate | + | PATS at some places still uses [[wp>MD5]] or [[wp>SHA1]] checksums |
- | ===== Creating | + | ===== Creating |
- | It is usually sufficient to use MD5 checksums and by default we expect | + | * Linux shell commands: shasum, openssl, sha512sum |
- | you to submit an MD5 checksum. It looks something like this: | + | |
- | < | + | * Windows command prompt: certUtil |
- | | + | |
- | </ | + | |
- | Please make sure you submit the // | + | |
- | In order to generate such a checksum you may use the following MD5 | + | ===== Creating SHA1 Checksums |
- | checksum generators: | + | |
- | * Linux | + | |
- | * md5sum command in shell | + | |
- | * Mac OS | + | |
- | * md5 command in terminal | + | |
- | * Windows | + | |
- | * MD5sums, http:// | + | |
- | * FCIV--File Checksum Integrity Verifier http:// | + | |
- | * Bitser, http:// | + | |
- | * FastSum, http:// | + | |
- | * Multiple OS | + | |
- | * JDigest, http:// | + | |
- | ===== Creating SHA1 Checksums ===== | + | * Linux shell commands: sha1sum, openssl |
+ | * Max OS terminal commands: openssl | ||
+ | * Windows command prompt: certUtil | ||
- | Alternatively you can also use SHA1 checksums. A SHA1 checksum looks something | + | ===== Creating MD5 Checksums (deprecated) ===== |
- | like this: | + | |
- | < | + | |
- | 74a0967932b807230873c3def8ffbcfe32d9b0f2 | + | |
- | </ | + | |
- | In order to generate such a checksum you may use the following SHA1 | + | |
- | checksum generators: | + | * Mac OS terminal commands: md5 |
- | | + | * Windows |
- | * sha1sum command in shell | + | |
- | * Max OS | + | |
- | * openssl in terimal, call as < | + | |
- | * Windows | + | |
- | * Bitser, http:// | + | |
- | * Multiple OS | + | |
- | * JDigest, http:// | + | |
- | + | ||
- | ===== Other Checksums ===== | + | |
- | + | ||
- | In exceptional circumstances alternative checksums that are at least | + | |
- | as reliable as an MD5 checksum may be acceptable (e.g. GNU-PG/PGP file | + | |
- | signatures). But please contact Frank Langbein early if you intend to | + | |
- | use one of these checksum mechanisms. | + | |