An md5sum compatibility option. It does absolutely nothing.
(md5sum uses -b to treat binary files differently from texts files.)
Check tthsum of all files listed in
file against the checksum listed in the same file. The actual format of that
file is the same as output of
tthsum. That is, each line in the file describes a file. A line looks like:
<TTH CHECKSUM> <FILENAME>
So, for example, if a file were created and its message digest calculated like so:
echo foo > tth-test-file; tthsum tth-test-file
tthsum would report:
See NOTES for more information on the digest file format.
to read the contents of the files to hash. Normally, using read is
cheaper. This all depends on system load, I/O speed, CPU speed,
L1 and/or L2 cache size and whatnot.
Show the progress. Print the percentage of completeness while hashing
on standard error. Prints file position instead of percentage when the
file size is unknown.
Be verbose. Print filenames when checking (with -c).
Warn on improperly formatted lines when checking (with -c).
Print a small help text or the version, respectively, on standard out.
If an unknown combination of options is encountered, the small help
is printed on standard error and
tthsum will return non-zero.
tthsum returns 0 if no error occurred or, when checking a digest, if at least one line is formatted properly and the TTHs of all properly formatted lines match. tthsum returns 2 if an unknown combination of options is encountered. In all other cases will tthsum return 1.
tthsum intentionally uses an interface identical to md5sum.
tthsum uses BASE32 encoding consisting of the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ234567. It will accept lower case letters in the digest input as well.
tthsum does not accept long options such as --help.
A digest file format line looks like: <BASE32><SPACES><FILENAME><EOL>. BASE32 is a 39 character long BASE32 encoded string. SPACES is a set of two spaces (0x20). FILENAME is the name of the file, encoded in UTF8 and with all control characters (those below 0x20) encoded as \xNN or \C C-style escapes. (The backslash is escaped as \\ as well. On Windows, backslashes in paths will be translated to slashes for compatibility with real operating systems.) EOL may be CRLF (\r\n), just plain LF (\n) or even nothing at end-of-file.
If you see warnings about an improper locale setup, check your LANG and/or LC_CTYPE environment variables. If these are not set properly, tthsum cannot represent non-ASCII characters (those above 0x7F) in UTF8. See locale(1) for more information or try to set LC_CTYPE to e.g. "en_US".
Report bugs to <email@example.com>.
Copyright © 2009 Walter Doekes. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
tthsum and this manpage were written by Walter Doekes (firstname.lastname@example.org). The hashing code was copied directly from DC++, an open source peer-to-peer file sharing program by Jacek Sieka (email@example.com) who had based the hashing code on the one used in BCDC++ (a modified DC++) by Dustin Brody (firstname.lastname@example.org). After version 1.1.0, the hashing code from the Tiger hash authors is used instead, to support big endian architectures and to remove the need for C++ compilers and libraries. The md5sum manpage, written by Juho Vuori (email@example.com), was used as a template. This manpage was proofread by Dustin Brody.
|tthsum version 1.3.2||TTHSUM (1)||Dec 2009|