Updates for release 4.3

jessekornblum · jessekornblum · commit ce4b4fe0196a · 2012-10-23T20:39:56.000Z
diff --git a/NEWS b/NEWS
@@ -1,9 +1,12 @@
-** Changes in version 4.3 (RBF DATE)
-
-* New Features
+** Changes in version 4.3 (24 Oct 2012)
 
 * Bug Fixes
 
+      Fixed check for endian-ness, affecting hash generation on
+      big-endian platforms.
+
+      Fixed minor bugs related to OpenSolaris.
+
 
 
 ** Changes in version 4.2 (11 Jun 2012)
diff --git a/configure.ac b/configure.ac
@@ -3,7 +3,7 @@
 #
 
 AC_PREREQ(2.57)
-AC_INIT([MD5DEEP],[4.3-001],[research@jessekornblum.com])
+AC_INIT([MD5DEEP],[4.3],[research@jessekornblum.com])
 AC_CONFIG_FILES([Makefile src/Makefile man/Makefile tests/Makefile tests/testfiles/Makefile ])
 AM_INIT_AUTOMAKE
 AC_CONFIG_HEADERS([config.h])
diff --git a/doc/changes.txt b/doc/changes.txt
@@ -1,3 +1,14 @@
+** Changes in version 4.3 (24 Oct 2012)
+
+* Bug Fixes
+
+      Fixed check for endian-ness, affecting hash generation on
+      big-endian platforms.
+
+      Fixed minor bugs related to OpenSolaris.
+
+
+
 ** Changes in version 4.2 (11 Jun 2012)
 
 * Bug Fixes
diff --git a/doc/hashdeep.html b/doc/hashdeep.html
@@ -267,7 +267,7 @@ <h2><a name='sect6' href='#toc6'>Known Issues</a></h2>
 <p> 
 <h2><a name='sect7' href='#toc7'>Reporting Bugs</a></h2>
 We take all bug reports <i>very</i> seriously. Any bug that
-jeopardizes the forensic integrity of this program could have serious consequenses
+jeopardizes the forensic integrity of this program could have serious consequences
 on  people&rsquo;s lives. When submitting a bug report, please include a description
 of the problem, how you found it, and your contact information. <p>
 Send bug
diff --git a/doc/index.html b/doc/index.html
@@ -32,7 +32,7 @@
 <body>
 
 <h1>
-md5deep and hashdeep - Latest version 4.2
+md5deep and hashdeep - Latest version 4.3
 </h1>
 
 <hr>
@@ -175,9 +175,9 @@ <h3> Stable Version </h3>
 
 <p>
 The latest stable versions of md5deep and hashdeep are 
-version 4.2
+version 4.3
 and were released on
-11 Jun 2012.
+24 Oct 2012.
 You can take a look at the 
 <a href="changes.txt">complete changelog</a>, but here are the 
 changes in the latest version:
@@ -191,7 +191,8 @@ <h4> New Features </h4>
 
 <h4> Bug Fixes </h4>
 <ul>
-<li> Updated Tiger code to produce correct hashes for files larger than 4GB. </li>
+<li> Proper hash generation on big endian systems</li>
+<li> Allows compilation on OpenSolaris </li>
 </ul>
 
 
diff --git a/doc/md5deep.html b/doc/md5deep.html
@@ -154,57 +154,58 @@ <h2><a name='sect2' href='#toc2'>Description</a></h2>
 
 <dt><b>-q</b> </dt>
 <dd>Quiet
-mode. File names are omitted from the output. 
+mode. File names are omitted from the output. Each hash is still followed
+by two spaces before the newline. 
 <p> </dd>
 
 <dt><b>-Z</b> </dt>
-<dd>Produces output in Triage
-format. Each line contans the file&rsquo;s size, a tab, a hash of the first 512
-bytes, a tab, the hash of the complete file, a tab, and the file name. These
-values are intended in increasing order of specificity. That is, two files
-with different sizes cannot possibly match. This is a fast comparison and
-should be done first. Next, two files  with different partial hashes cannot
-possibly match. This is often  faster than hashing the whole file. Finally,
-if those two pieces align, then it&rsquo;s worth reading and hashing the entire
-file. 
+<dd>Produces output in Triage format. Each
+line contans the file&rsquo;s size, a tab, a hash of the first 512 bytes, a tab,
+the hash of the complete file, a tab, and the file name. These values are
+intended in increasing order of specificity. That is, two files with different
+sizes cannot possibly match. This is a fast comparison and should be done
+first. Next, two files  with different partial hashes cannot possibly match.
+This is often  faster than hashing the whole file. Finally, if those two
+pieces align, then it&rsquo;s worth reading and hashing the entire file. 
 <p> </dd>
 
 <dt><b>-0</b> </dt>
-<dd>Uses a NULL character (/0) to terminate each line instead of a
-newline. Useful for processing filenames with strange characters. 
+<dd>Uses
+a NULL character (/0) to terminate each line instead of a newline. Useful
+for processing filenames with strange characters. 
 <p> </dd>
 
 <dt><b>-l</b> </dt>
-<dd>Enables
-relative file paths. Instead of printing the absolute path for each file,
-displays the relative file path as indicated on the command  line. This
-flag may not be used in conjunction with the -b flag. 
+<dd>Enables relative file
+paths. Instead of printing the absolute path for each file, displays the
+relative file path as indicated on the command  line. This flag may not
+be used in conjunction with the -b flag. 
 <p> </dd>
 
 <dt><b>-b</b> </dt>
-<dd>Enables bare mode.
-Strips any leading directory information from  displayed filenames. This
-flag may not be used in conjunction with the -l flag. 
+<dd>Enables bare mode. Strips any
+leading directory information from  displayed filenames. This flag may not
+be used in conjunction with the -l flag. 
 <p> </dd>
 
 <dt><b>-k</b> </dt>
-<dd>Enables asterisk
-mode. An asterisk is inserted in lieu of a second space between the filename
-and the hash, just like md5sum in  its binary (-b) mode. 
+<dd>Enables asterisk mode. An asterisk
+is inserted in lieu of a second space between the filename and the hash,
+just like md5sum in  its binary (-b) mode. 
 <p> </dd>
 
 <dt><b>-c</b> </dt>
-<dd>Enables comma
-separated values output, or CSV mode. This mode has the side effect of removing
-the 10 digit size limitation from -z mode. Also note that asterisks from
--k mode are not displayed when in CSV mode. 
+<dd>Enables comma separated values
+output, or CSV mode. This mode has the side effect of removing the 10 digit
+size limitation from -z mode. Also note that asterisks from -k mode are not
+displayed when in CSV mode. 
 <p> </dd>
 
 <dt><b>-o</b> &lt;bcpflsd&gt; </dt>
-<dd>Enables expert mode.
-Allows the user specify which (and only which) types of files are processed.
-Directory processing is still controlled with the -r flag. The expert mode
-options allowed are: <br>
+<dd>Enables expert mode. Allows the user
+specify which (and only which) types of files are processed. Directory processing
+is still controlled with the -r flag. The expert mode options allowed are:
+<br>
 f - Regular files <br>
 b - Block Devices <br>
 c - Character Devices <br>
@@ -311,7 +312,7 @@ <h2><a name='sect6' href='#toc6'>Known Issues</a></h2>
 <h2><a name='sect7' href='#toc7'>Reporting Bugs</a></h2>
 We
 take all bug reports <i>very</i> seriously. Any bug that jeopardizes the forensic
-integrity of this program could have serious consequenses on  people&rsquo;s lives.
+integrity of this program could have serious consequences on  people&rsquo;s lives.
 When submitting a bug report, please include a description of the problem,
 how you found it, and your contact information. <p>
 Send bug reports to the
diff --git a/man/hashdeep.1 b/man/hashdeep.1
@@ -1,4 +1,4 @@
-.TH HASHDEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH HASHDEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 hashdeep \- Compute, compare, or audit multiple message digests
diff --git a/man/md5deep.1 b/man/md5deep.1
@@ -1,4 +1,4 @@
-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 md5deep \- Compute and compare MD5 message digests
diff --git a/man/sha1deep.1 b/man/sha1deep.1
@@ -1,4 +1,4 @@
-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 md5deep \- Compute and compare MD5 message digests
@@ -326,7 +326,7 @@ If you need to do this, use the \fBfind\fR(1) command.
 
 .SH REPORTING BUGS
 We take all bug reports \fIvery\fR seriously. Any bug that jeopardizes the
-forensic integrity of this program could have serious consequenses on 
+forensic integrity of this program could have serious consequences on 
 people's lives. When submitting a bug report, please include a description
 of the problem, how you found it, and your contact information.
 .PP
diff --git a/man/sha256deep.1 b/man/sha256deep.1
@@ -1,4 +1,4 @@
-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 md5deep \- Compute and compare MD5 message digests
@@ -326,7 +326,7 @@ If you need to do this, use the \fBfind\fR(1) command.
 
 .SH REPORTING BUGS
 We take all bug reports \fIvery\fR seriously. Any bug that jeopardizes the
-forensic integrity of this program could have serious consequenses on 
+forensic integrity of this program could have serious consequences on 
 people's lives. When submitting a bug report, please include a description
 of the problem, how you found it, and your contact information.
 .PP
diff --git a/man/tigerdeep.1 b/man/tigerdeep.1
@@ -1,4 +1,4 @@
-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 md5deep \- Compute and compare MD5 message digests
@@ -326,7 +326,7 @@ If you need to do this, use the \fBfind\fR(1) command.
 
 .SH REPORTING BUGS
 We take all bug reports \fIvery\fR seriously. Any bug that jeopardizes the
-forensic integrity of this program could have serious consequenses on 
+forensic integrity of this program could have serious consequences on 
 people's lives. When submitting a bug report, please include a description
 of the problem, how you found it, and your contact information.
 .PP
diff --git a/man/whirlpooldeep.1 b/man/whirlpooldeep.1
@@ -1,4 +1,4 @@
-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"
+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"
 
 .SH NAME
 md5deep \- Compute and compare MD5 message digests
@@ -326,7 +326,7 @@ If you need to do this, use the \fBfind\fR(1) command.
 
 .SH REPORTING BUGS
 We take all bug reports \fIvery\fR seriously. Any bug that jeopardizes the
-forensic integrity of this program could have serious consequenses on 
+forensic integrity of this program could have serious consequences on 
 people's lives. When submitting a bug report, please include a description
 of the problem, how you found it, and your contact information.
 .PP
diff --git a/src/files.cpp b/src/files.cpp
@@ -91,7 +91,7 @@ typedef struct _ENCASE_HASH_HEADER {
 #define HASH_STRING_LENGTH   (hashes[opt_md5deep_mode_algorithm].bit_length/4)
 
 /****************************************************************
- *** SUpport
+ *** Support Functions
  ****************************************************************/
 
 // Find the index of the next comma in the string str starting at index start.

Original file line number	Diff line number	Diff line change
`@@ -3,7 +3,7 @@`
`3`	`3`	`#`
`4`	`4`
`5`	`5`	`AC_PREREQ(2.57)`
`6`		`-AC_INIT([MD5DEEP],[4.3-001],[[email protected]])`
	`6`	`+AC_INIT([MD5DEEP],[4.3],[[email protected]])`
`7`	`7`	`AC_CONFIG_FILES([Makefile src/Makefile man/Makefile tests/Makefile tests/testfiles/Makefile ])`
`8`	`8`	`AM_INIT_AUTOMAKE`
`9`	`9`	`AC_CONFIG_HEADERS([config.h])`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-.TH HASHDEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"`
	`1`	`+.TH HASHDEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"`
`2`	`2`
`3`	`3`	`.SH NAME`
`4`	`4`	`hashdeep \- Compute, compare, or audit multiple message digests`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-.TH MD5DEEP "1" "v4.3 \- RBF DATE" "AFOSI" "United States Air Force"`
	`1`	`+.TH MD5DEEP "1" "v4.3 \- 24 Oct 2012" "AFOSI" "United States Air Force"`
`2`	`2`
`3`	`3`	`.SH NAME`
`4`	`4`	`md5deep \- Compute and compare MD5 message digests`