{
    "mode": "info",
    "parameter": "md5sum",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/md5sum/json",
    "generated": "2026-11-12T22:21:52Z",
    "sections": {
        "File: coreutils.info,  Node: md5sum invocation,  Next: b2sum invocation,  Prev: cksum invocation,  Up: Summarizing files": {
            "content": "",
            "subsections": [
                {
                    "name": "6.4 'md5sum': Print or check MD5 digests",
                    "content": "'md5sum' computes a 128-bit checksum (or \"fingerprint\" or\n\"message-digest\") for each specified FILE.\n\nNote: The MD5 digest is more reliable than a simple CRC (provided by\nthe 'cksum' command) for detecting accidental file corruption, as the\nchances of accidentally having two files with identical MD5 are\nvanishingly small.  However, it should not be considered secure against\nmalicious tampering: although finding a file with a given MD5\nfingerprint is considered infeasible at the moment, it is known how to\nmodify certain files, including digital certificates, so that they\nappear valid when signed with an MD5 digest.  For more secure hashes,\nconsider using SHA-2, or the newer 'b2sum' command.  *Note sha2\nutilities::.  *Note b2sum invocation::.\n\nIf a FILE is specified as '-' or if no files are given 'md5sum'\ncomputes the checksum for the standard input.  'md5sum' can also\ndetermine whether a file and checksum are consistent.  Synopsis:\n\nmd5sum [OPTION]... [FILE]...\n\n'md5sum' uses the 'Untagged output format' for each specified file,\nas described at *note cksum output modes::.\n\nThe program accepts *note cksum common options::.  Also see *note\nCommon options::.\n\nAn exit status of zero indicates success, and a nonzero value\nindicates failure.\n"
                }
            ]
        }
    },
    "flags": [],
    "examples": [],
    "see_also": []
}