GOSTSUM(1)

πŸ’– GOSTSUM(1) β€” Debian GNU/Linux girlies rise up πŸ’–

okay so real quick, this whole thing is the GOSTSUM(1) page from Debian GNU/Linux, and it's lowkey iconic. buckle up bestie, we're hashing πŸŽ€


✨ NAME ✨

gostsum β€” generates or checks GOST R34.11-94 message digests πŸ¦‹


🌸 SYNOPSIS 🌸

gostsum [-bvt] [-c [file]] | [file...]

πŸ’… DESCRIPTION πŸ’…

so gostsum generates or checks GOST hash sums. the algorithm it uses to generate them is reasonably fast and strong enough for most cases, no cap. the exact specification of the algorithm lives in GOST R34.11-94, iykyk.

normally gostsum generates checksums of all the files you hand it as parameters and prints the checksums followed by the filenames. cute, simple, slay.

but if you specify -c, only one filename parameter is allowed. that file should contain checksums and the filenames those checksums refer to, and then the files listed in that file get checked against the checksums listed in there. peek at option -c below for the whole tea.


πŸ‘‘ OPTIONS πŸ‘‘

  • -b β€” use binary mode. in a unix environment, the only difference between this and normal mode is an asterisk * preceding the filename in the output. that's it. that's the whole vibe shift. ✨
  • -c β€” check gost hashes of all files listed in file against the checksum listed in that same file. the actual format of that file is the same as the output of md5sum. that is, each line in the file describes a file. a line looks like:
<hashsum> <filename>

so, for example, if a file was created and its message digest calculated like so:

echo foo > hash-test-file; gostsum hash-test-file

gostsum would report:

1541e09d0aa5971f732991ae1bdfb63f2609edd7536b40f8c2ae7c1e2f99e072  hash-test-file

like. it ate. πŸ’–

  • -v β€” be more verbose. print filenames when checking (that's when you're using -c). yes queen, give us the detail.
  • -t β€” use the test parameter set. here's the deal: gostsum supports two sets of parameters (which are really parameters of the GOST 28147-89 block cipher) specified in the IETF draft draft-popov-cryptopro-cpalgs-02.txt. by default, the cryptopro paramset is used. this option enables use of the test paramset as specified in the appendices to the GOST. two sets, pick your fighter 🫢

😭 CAVEATS 😭

the output of gost12sum has a reversed byte order compared to the output of the openssl dgst command because of the Russian GOST requrements. yes that's a real thing that happens. don't come for me, come for the byte order πŸ’€


πŸ™ˆ BUGS πŸ™ˆ

this manpage is not quite accurate and has formatting inconsistent with other manpages. (not me exposing myself πŸ’…)

gostsum does not accept standard options like --help. nope. it simply will not. periodt.


🌈 AUTHOR 🌈

Victor Wagner <vitus@wagner.pp.ru>


πŸŽ€ SEE ALSO πŸŽ€

(there isn't one in this page bestie, we're on our own and honestly? thriving πŸ¦‹)


and that's the whole page!! thank you for coming to my ted talk. this was the GOSTSUM(1) manual, and the source/version + date for it is Openssl, 02 Aug 2017, back when it was GOSTSUM(1) all the way down. mwah πŸ’‹ stay hashing, stay hydrated, and remember: reverse those bytes responsibly 🧚