Compute checksums using the specified digest algorithm.
Supported legacy checksums (which are not supported by --check):
‘sysv’ equivalent to
sum -s‘bsd’ equivalent to
sum -r‘crc’ equivalent to
Supported more modern digest algorithms are:
‘md5’ equivalent to
md5sum‘sha1’ equivalent to
sha1sum‘sha224’ equivalent to
sha224sum‘sha256’ equivalent to
sha256sum‘sha384’ equivalent to
sha384sum‘sha512’ equivalent to
sha512sum‘blake2b’ equivalent to
b2sum‘sm3’ only available through
Print base64-encoded digests not hexadecimal. This option is ignored with --check. The format conforms to RFC 4648#4.
Note that each base64-encoded digest has zero, one or two trailing padding (‘=’) bytes. The length of that padding is the checksum-bit-length modulo 3, and the --check parser requires precisely the same input digest string as what is output. I.e., removing or adding any ‘=’ padding renders a digest non-matching.
Output extra information to stderr, like the checksum implementation being used.
Change (shorten) the default digest length. This is specified in bits and thus must be a multiple of 8. This option is ignored when --check is specified, as the length is automatically determined when checking.
Print only the unencoded raw binary digest for a single input.
Do not output the file name or anything else.
Use network byte order (big endian) where applicable:
for ‘bsd’, ‘crc’, and ‘sysv’.
This option works only with a single input.
Unlike other output formats,
cksum provides no way to
--check a --raw checksum.
Output using the original Coreutils format used by the other
standalone checksum utilities like
md5sum for example.
This format has the checksum at the start of the line, and may be
more amenable to further processing by other utilities,
especially in combination with the --zero option.
Note this does not identify the digest algorithm used for the checksum.
See cksum output modes for details of this format.