Browse files

Version 2.0

  • Loading branch information...
jessekornblum committed Feb 23, 2008
1 parent c05f43d commit 5d8b5ef4d93d9d0c8c7b4c7fe455a756760d0106
Showing with 17,033 additions and 975 deletions.
  1. +1 −0 AUTHORS
  2. +366 −0 COPYING
  3. +50 −0 ChangeLog
  4. +229 −0 INSTALL
  5. +85 −0
  6. +605 −0
  7. +343 −0 NEWS
  8. +30 −120 README
  9. +30 −0 TODO
  10. +836 −0 aclocal.m4
  11. +1,388 −0 config.guess
  12. +151 −0
  13. +1,489 −0 config.sub
  14. +7,392 −0 configure
  15. +70 −0
  16. +37 −19 cycles.c
  17. +423 −0 depcomp
  18. +251 −118 dig.c
  19. +120 −76 files.c
  20. +138 −145 hash.c
  21. +6 −3 hashTable.c
  22. +6 −30 hashTable.h
  23. +120 −62 helpers.c
  24. +251 −0 install-sh
  25. +127 −51 main.c
  26. +253 −166 main.h
  27. +104 −6 match.c
  28. +67 −20 md5.c
  29. +25 −15 md5.h
  30. +18 −11 md5deep.1
  31. +336 −0 missing
  32. +99 −0 mkinstalldirs
  33. +54 −5 sha1.c
  34. +24 −17 sha1.h
  35. +279 −0 sha1deep.1
  36. +66 −22 sha256.c
  37. +33 −23 sha256.h
  38. +279 −0 sha256deep.1
  39. +73 −0 tchar-local.h
  40. +72 −32 tiger.c
  41. +25 −15 tiger.h
  42. +279 −0 tigerdeep.1
  43. +50 −2 ui.c
  44. +43 −4 whirlpool.c
  45. +31 −13 whirlpool.h
  46. +279 −0 whirlpooldeep.1
@@ -0,0 +1 @@
+md5deep was written by Jesse Kornblum,

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -0,0 +1,50 @@
+2007-09-26 Jesse Kornblum <>
+ * Added second ioctl call in Linux version of find_file_size
+ to get the true sector size; don't just assume 512 byte
+ sectors.
+ * Changed fseek call in hash.c to fseeko for large file support
+ * Removed spurrious -u: from getopt call in main.c
+ * Removed function checks from We weren't using
+ them to build support, so we shouldn't waste time checking
+ for them.
+2007-09-25 Jesse Kornblum <>
+ * Created new function print_error_unicode to
+ handle errors encountered while processing
+ files with (possibly) Unicode characters in
+ their filenames.
+ * Added AC_SYS_LARGEFILE to configure script to
+ account for large files on Linux. This fixes
+ the file estimation mode (-e) for Liunx.
+ * Fixed find_file_size for block devices on OS X.
+2007-09-24 Jesse Kornblum <>
+ * Updated error display for Unicode filenames in dig.c
+ * Fixed expert mode due to 64-bit values in int returns
+2007-09-23 Jesse Kornblum <>
+ * Reverted back to old method of installing man pages.
+ When make install is invoked, current md5deep.1 is
+ copied over other man pages, which are all then
+ installed normally.
+2007-09-22 Jesse Kornblum <>
+ * Switched to GNU autotools
+ * Moved list of past changes to NEWS file
@@ -0,0 +1,229 @@
+Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+Basic Installation
+ These are generic installation instructions.
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+ The file `' (or `') is used to create
+`configure' by a program called `autoconf'. You only need
+`' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+The simplest way to compile this package is:
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+ 2. Type `make' to compile the package.
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+Compilers and Options
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+ *Note Defining Variables::, for more details.
+Compiling For Multiple Architectures
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+Installation Names
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+Optional Features
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+Specifying the System Type
+ There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+where SYSTEM can have one of these forms:
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+ If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+Sharing Defaults
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/' if it exists, then
+`PREFIX/etc/' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+Defining Variables
+ Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+ ./configure CC=/usr/local2/bin/gcc
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+`configure' Invocation
+ `configure' recognizes the following options to control how it
+ Print a summary of the options to `configure', and exit.
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+ Alias for `--cache-file=config.cache'.
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
@@ -0,0 +1,85 @@
+bin_PROGRAMS=md5deep sha1deep sha256deep tigerdeep whirlpooldeep
+base_src=main.c dig.c cycles.c hash.c ui.c helpers.c files.c \
+ match.c hashTable.c \
+ md5.h sha1.h sha256.h tiger.h whirlpool.h \
+ main.h tchar-local.h hashTable.h
+md5deep_SOURCES =${base_src} md5.c
+sha1deep_SOURCES =${base_src} sha1.c
+sha256deep_SOURCES =${base_src} sha256.c
+tigerdeep_SOURCES =${base_src} tiger.c
+whirlpooldeep_SOURCES=${base_src} whirlpool.c
+# We erase the old man pages, just in case they might be symbolic links
+# (symbolic links were used in a previous release)
+install-exec-hook: update-manpages
+ rm -f ${man1dir}/${ALL_GOALS}deep.1
+update-manpages: md5deep.1
+ cp md5deep.1 sha1deep.1
+ cp md5deep.1 sha256deep.1
+ cp md5deep.1 tigerdeep.1
+ cp md5deep.1 whirlpooldeep.1
+man_MANS=md5deep.1 sha1deep.1 sha256deep.1 tigerdeep.1 whirlpooldeep.1
+EXTRA_DIST=${man_MANS} config.guess config.sub
+ rm -f *~
+ @grep RBF *.c *.h ${man_MANS} AUTHORS README NEWS TODO ChangeLog
+ @grep TODO *.c *.h ${man_MANS} AUTHORS README NEWS ChangeLog
+ @echo
+ @echo From TODO file:
+ @cat TODO
+ aclocal && autoconf && autoheader && automake && ./config.status
+# This Makefile is designed to package Windows distributions from Mac OS X
+# To do this on a Linux box, The big line below starting with "/usr/bin/tbl"
+# should be replaced with:
+# man ./$(MAN_PAGE) | col -bx > README.txt
+# and the "flip -d" command should be replaced with unix2dos. Note that
+# these commands are included below but are commented out.
+# The flip command can be found at:
+ flip -d CHANGES.TXT
+# unix2dos CHANGES.TXT
+ /usr/bin/tbl ./$(man_MANS) | /usr/bin/groff -S -Wall -mtty-char -mandoc -Tascii | /usr/bin/col -bx > README.TXT
+ flip -d README.TXT
+# man ./md5deep.1 | col -bx > README.TXT
+# unix2dos README.TXT
+cross: ${WINDOC}
+ ./configure --host=mingw32
+ make all
+ mingw32-strip ${ALL_GOALS}deep.exe
+ zip -9 md5deep-${VERSION}.zip ${ALL_GOALS}deep.exe $(WINDOC)
+ rm -f ${WINDOC}
+ make distclean
+world: dist cross
+MAINTAINERCLEANFILES= md5deep-${VERSION}.zip md5deep-${VERSION}.tar.gz \
+ ${ALL_GOALS}deep.exe
Oops, something went wrong.

0 comments on commit 5d8b5ef

Please sign in to comment.