rdd-verify(1) [debian man page]
VERIFIER(1) General Commands Manual VERIFIER(1) NAME
rdd-verify - verifies checksums and hash values generated by rdd-copy(1) SYNOPSIS
rdd-verify [OPTION] file1 ... DESCRIPTION
Rdd-verify verifies checksums and hash values generated by rdd-copy(1). Rdd stores checksums (Adler32 or CRC32) in files. These files must be passed to rdd-verify for verification. Hash values (MD5 or SHA1) computed by rdd-copy(1) must be passed to rdd-verify on the command line as hexadecimal strings. Rdd-verify reads all input files (file1, ...) and recomputes the checksums and hash values that the user wishes to verify. The verifica- tion will very likely fail if the concatenation of the input files is different from the source that was copied by rdd-copy(1). OUTPUT
All verification errors are reported on stderr. OPTIONS
-?, --help Print a usage message. -V, --version Report version number and exit. -v, --verbose Be verbose (more messages). -v, --verbose Be verbose (more messages). --checksum, --adler32 file Verify the Adler32 checksums stored in file. --crc, --crc32 file Verify the CRC32 checksums stored in file. --md5, --md5 digest Recompute the MD5 hash value. It should be equal to digest. --sha, --sha1 digest Recompute the SHA1 hash value. It should be equal to digest. A digest argument is a hexadecimal string. Leading zeroes may not be omitted. EXAMPLES
rdd-verify --md5 0123456789abcdef0123456789abcdef disk.img Compute the MD5 hash value over disk.img and verify whether it equals 0123456789abcdef0123456789abcdef. rdd-verify --adler32 checksums.a32 disk.img Compute the adler32 checksums over disk.img and compare each checksum to the corresponding checksum in checksums.a32. SEE ALSO
rdd-copy(1) REPORTING BUGS
Report bugs to <rdd@holmes.nl>. ACKNOWLEDGEMENTS
Many thanks to all who reported bugs and successes, and who suggested improvements. You know who you are. COPYRIGHT
Copyright (C) 2002-2003 Netherlands Forensic Institute This software comes with NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. rdd-verify February 2002 VERIFIER(1)
Check Out this Related Man Page
DGST(1) OpenSSL DGST(1) NAME
dgst, md5, md4, md2, sha1, sha, mdc2, ripemd160 - message digests SYNOPSIS
openssl dgst [-md5|-md4|-md2|-sha1|-sha|-mdc2|-ripemd160|-dss1] [-c] [-d] [-hex] [-binary] [-out filename] [-sign filename] [-verify file- name] [-prverify filename] [-signature filename] [file...] [md5|md4|md2|sha1|sha|mdc2|ripemd160] [-c] [-d] [file...] DESCRIPTION
The digest functions output the message digest of a supplied file or files in hexadecimal form. They can also be used for digital signing and verification. OPTIONS
-c print out the digest in two digit groups separated by colons, only relevant if hex format output is used. -d print out BIO debugging information. -hex digest is to be output as a hex dump. This is the default case for a "normal" digest as opposed to a digital signature. -binary output the digest or signature in binary form. -out filename filename to output to, or standard output by default. -sign filename digitally sign the digest using the private key in "filename". -verify filename verify the signature using the the public key in "filename". The output is either "Verification OK" or "Verification Failure". -prverify filename verify the signature using the the private key in "filename". -signature filename the actual signature to verify. -rand file(s) a file or files containing random data used to seed the random number generator, or an EGD socket (see RAND_egd(3)). Multiple files can be specified separated by a OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others. file... file or files to digest. If no files are specified then standard input is used. NOTES
The digest of choice for all new applications is SHA1. Other digests are however still widely used. If you wish to sign or verify data using the DSA algorithm then the dss1 digest must be used. A source of random numbers is required for certain signing algorithms, in particular DSA. The signing and verify options should only be used if a single file is being signed or verified. 0.9.7d 2002-04-30 DGST(1)