checksums [PATS2]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== File Checksums ======

A [[wp>checksum]] (or hash) is a datum computed from digital data to verify the integrity of that data. Typically you use a program to calculate the checksum of a file. Then after this file has been transmitted to another 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 or in other ways.

You should **use [[wp>SHA2]]** checksums, specifically sha512 (to keep things simple), **in case of submission problems**, etc., as described in the [[Submission Guide]]. Alternatively, you can also use **[[wp>SHA3]]** or an **OpenPGP** file signature with your key published to the OpenPGP key servers. For other checksums, please first check with the project coordinator.

PATS at some places still uses [[wp>MD5]] or [[wp>SHA1]] checksums due to legacy reasons. These can be used to verify that there were no accidental transmission errors but are otherwise **deprecated**. They cannot be used to verify that offline archives have been transmitted before the deadline as they are cryptographically broken. Note that PATS modifies some files after submission (files in the document section are specially processed and changed, and some archive files are converted to zip for compatibility).

===== Creating SHA2 Checksums =====

  * Linux shell commands: shasum, openssl, sha512sum
  * Mac OS terminal commands: shasum, openssl
  * Windows command prompt: certUtil

===== Creating SHA1 Checksums (deprecated) =====

  * Linux shell commands: sha1sum, openssl
  * Max OS terminal commands: openssl
  * Windows command prompt: certUtil

===== Creating MD5 Checksums (deprecated) =====

  * Linux shell commands: md5sum
  * Mac OS terminal commands: md5
  * Windows command prompt: certUtil
Site Tools

Page Tools
