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)

CKSFV(1)						      General Commands Manual							  CKSFV(1)

NAME

       cksfv - tests and creates simple file verification (SFV) listings

SYNOPSIS

       cksfv [-bciqrL] [-C dir] [-f file] [-g path] [file ...]

DESCRIPTION

       cksfv  is  a tool for verifying CRC32 checksums of files. CRC32 checksums are used to verify that files are not corrupted. The algorithm is
       cryptographically crippled so it can not be used for security purposes.	md5sum (1) or sha1sum (1) are much better  tools  for  checksuming
       files. cksfv should only be used for compatibility with other systems.

       cksfv has two operation modes: checksum creation and checksum verification

       In checksum creation mode cksfv outputs CRC32 checksums of files to to stdout, normally redirected to an .sfv file.

       In  checksum verification mode  cksfv reads filenames from an sfv file, and compares the recorded checksum values against recomputed check-
       sums of files.

OPTIONS

       These options are available

       -b     Strip dirnames from filenames that are checksumed. loads the files from original positions, but prints only basenames  to  catalogue
	      in sfv file.

       -c     Use  stdout  for	printing  progress  and  final resolution (files OK or some errors detected). This is useful for external programs
	      analysing output of cksfv. This also forces fflushes on the output when needed.

       -C dir  Change current directory before proceeding with a verification operation.  This option is mostly obsoleted with -g option.  Earlier
	      this was used to verify checksums in a different directory: cksfv -C foo -f foo/bar.sfv

       -f file
	      Verify checksums in the sfv file

       -g file
	      Change current directory to the path name of the file and verify checksums in the sfv.

       -i     Ignore case in filenames. This is used in the checksum verification mode.

       -L     Follow symlinks when recursing subdirectories. This option is used with the -r option.

       -q     Enable QUIET mode (instead of verbose mode), only error messages are printed

       -v     Enable VERBOSE mode, this is the default mode

       -r     recurse  directories  and check the .sfv files in each. Symlinks are not followed by default. This option cannot be used with -f and
	      -g options.

EXAMPLES

       Verify checksums of files listed in 'foo/files.sfv':
       cksfv -g foo/files.sfv

       Create checksums for a set of files:
       cksfv *.gz > files.sfv

       Verify checksums of case-insensitive filenames listed in 'files.sfv'.
       This is sometimes useful with files created by operating systems
       that have case-insensitive filesystem names.
       cksfv -i -g files.sfv

       Check checksums of files 'foo' and 'bar' listed in 'files.sfv':
       cksfv -g files.sfv foo bar

       Create checksums of files matching /foo/bar/* and strip dirnames away:
       cksfv -b /foo/bar/* > files.sfv

       Recursively scan /foo/bar and verify each .sfv file:
       cksfv -C /foo/bar -r

       Same as previous, but starting from the current working directory
       and also following symlinks during recursion:
       cksfv -r -L

SEE ALSO

       basename(1) dirname(1) md5sum(1) sha1sum(1)

AUTHOR

       This manual page  was  originally  written  by  Stefan  Alfredsson  <stefan@alfredsson.org>.   It  was  later  modified	by  Heikki  Orsila
       <heikki.orsila@iki.fi> and Durk van Veen <durk.van.veen@gmail.com>.

																	  CKSFV(1)