Autopatrolled, Extended confirmed users, IP block exemptions, Pending changes reviewers, Rollbackers
465,230
edits
(Undid revision 916302136 by 72.33.2.146 (talk) Datum is the singular form.) 
GoingBatty (talk  contribs) m (→top: General fixes) 

{{Multiple issues
{{
{{one sourcedate=October 2018}}
}}
[[File:Checksum.svgthumb330pxrightEffect of a typical checksum function (the Unix <tt>[[cksum]]</tt> utility)]]
The actual [[algorithmprocedure]] which yields the checksum from a data input is called a '''checksum function''' or '''[[checksum algorithm]]'''. Depending on its design goals, a good checksum algorithm will usually output a significantly different value, even for small changes made to the input. This is especially true of [[cryptographic hash function]]s, which may be used to detect many data corruption errors and verify overall [[data integrity]]; if the computed checksum for the current data input matches the stored value of a previously computed checksum, there is a very high probability the data has not been accidentally altered or corrupted.
Checksum functions are related to [[hash function]]s, [[fingerprint (computing)fingerprint]]s, [[randomization function]]s, and [[cryptographic hash function]]s. However, each of those concepts has different applications and therefore different design goals. For instance, a function returning the start of a string can provide a hash appropriate for some applications but will never be a suitable checksum. Checksums are used as [[
[[Check digit]]s and [[parity bit]]s are special cases of checksums, appropriate for small blocks of data (such as [[Social Security number]]s, [[bank account]] numbers, [[Word (data type)computer word]]s, single [[byte]]s, etc.). Some [[errorcorrecting code]]s are based on special checksums which not only detect common errors but also allow the original data to be recovered in certain cases.
