SHA1SUM(1)
π
SHA1SUM(1) β okay so bestie, let's talk about sha1sum β¨
hi hi hiii π«Ά you found the manual page for sha1sum, and honestly? iconic. she's a legacy queen, she's been around forever, and she still shows up to work every day. let's get into it π
NAME π
sha1sum β compute and check SHA1 message digest. that's it, that's the whole job. no cap. β¨
SYNOPSIS πΈ
sha1sum [OPTION]... [FILE]...
DESCRIPTION π¦
so what she actually does: she prints or checks SHA1 (160-bit) checksums. she's the legacy interface to the cksum utility β like, the original, the blueprint, the blueprint-adjacent icon. π
and here's the vibe with the arguments: with no FILE, or when FILE is -, she reads from standard input. yes, literally - means "stdin bestie". stdin always understood the assignment. π₯°
okay, the options. here we go, don't scroll away:
-b,--binaryβ read in binary mode-c,--checkβ read checksums from the FILEs and check them. this is the "am I being lied to?" mode π--tagβ create a BSD-style checksum-t,--textβ read in text mode, and yes this is the default-z,--zeroβ end each output line with NUL, not newline, and disable file name escaping. NUL, not newline. she's not like other girls π
the next five are only useful when verifying checksums π
okay bestie, listen, these five are specifically for the checking era of your life. if you're not verifying, they're just standing there being pretty:
--ignore-missingβ don't fail or report status for missing files--quietβ don't print OK for each successfully verified file--statusβ don't output anything, status code shows success--strictβ exit non-zero for improperly formatted checksum lines-w,--warnβ warn about improperly formatted checksum lines
--helpβ display this help and exit--versionβ output version information and exit
the ~lore~ of how the sums work π§
the sums are computed as described in FIPS-180-1. when checking, the input should be a former output of this program β like, she only trusts her own receipts. π
the default mode is to print a line with: checksum, a space, a character indicating input mode (* for binary, for text or where binary is insignificant), and name for each FILE. so like:
checksum *filename
or
checksum filename
one little asterisk and suddenly everything means something. it's giving detail-oriented. π
and on GNU systems? there is no difference between binary mode and text mode. none. zero. they're the same picture. π
BUGS π
okay so this is the serious part and I need you to actually read it:
Do not use the MD5 algorithm for security related purposes. instead, use an SHA-2, SHA-3, or BLAKE2 algorithm, implemented in the cksum(1) program. fr fr, protect yourself. π₯
AUTHOR π
Written by Ulrich Drepper, Scott Miller, and David Madore. legends, all three. π
REPORTING BUGS π
found something broken? tell the girlies:
- Report bugs to:
bug-coreutils@gnu.org - GNU coreutils home page:
https://www.gnu.org/software/coreutils/ - General help using GNU software:
https://www.gnu.org/gethelp/ - Report any translation bugs to:
https://translationproject.org/team/
SEE ALSO π
cksum(1)- Full documentation
https://www.gnu.org/software/coreutils/sha1sum - or available locally via:
info '(coreutils) sha1sum invocation'
π and that's the page, bestie
cute little sign-off real quick: this package was Packaged by Ubuntu (9.10-1ubuntu2), and the copyright reads Copyright Β© 2026 Free Software Foundation, Inc. π
the license is GPLv3+: GNU GPL version 3 or later β https://gnu.org/licenses/gpl.html. this is free software: you are free to change and redistribute it. and it says, and I quote, there is NO WARRANTY, to the extent permitted by law. π«Ά
all of this is from GNU coreutils 9.10, dated August 2026. slay, go compute a checksum, ily πβ¨π
π¦ where this page comes from
- ubuntu stonking: gnu-coreutils 9.10-1ubuntu2 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms