dc3dd  7.2.646
About: dc3dd is patch to the GNU dd program that has several features intended for forensic acquisition of data (including hashing on-the-fly, split output files, pattern writing, a progress meter, and file verification).
  Fossies Dox: dc3dd-7.2.646.zip  ("unofficial" and yet experimental doxygen-generated source code documentation)  

dc3dd Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies dc3dd-7.2.646.zip contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
dc3dd 7.2.640

When imaging to a device with verification under Mac OS X, verification
can fail due to automatic mounting of the target device. One solution is
to use Disk Arbitrator in conjunction with dc3dd on OS X.    

New Features:
Log output may be sent to multiple job logs and hash logs. Simply specify
log=LOG and/or hlog=LOG more than once.

Verification of an image restored to a device larger than the image is now
supported. Specify hof=DEVICE to hash only the bytes dc3dd writes to the
device. Specify fhod=DEVICE to hash both the bytes dc3dd writes to the
device and all the bytes that follow, up to the end of the device.   

Specifying hof=DEVICE will now default to phod=DEVICE behavior (hash only 
the bytes output by dc3dd, not the full device).

Building dc3dd:
dc3dd is distributed as source code and must be compiled before use.
The default configuration can be built and installed to /usr/local/bin
with the following commands:

$ tar zxvf dc3dd-7.2.640.tar.gz
$ cd dc3dd-7.2.640
$ ./configure
$ make
$ sudo make install

Note that autoconf-1.10.1 and gperf may need to be installed prior to
execution of the above commands.

dc3dd can be customized at compile-time with various options.
The available options are as follows, and can be verified after
compilation using the --flags command line option: 

(equivalent to hash=md5 command-line option)

(equivalent to hash=sha1 command-line option)

(equivalent to hash=sha256 command-line option)

(equivalent to hash=sha512 command-line option)

(equivalent to ofsz=BYTES command-line option)

(equivalent to verb=on command-line option)

(equivalent to nwspc=on command-line option)

(equivalent to dbr=on command-line option)

Enable checking ATA/SATA drives for hidden areas
No command-line equivalent, cannot be overridden.

These options are enabled by including them in the CFLAGS argument to
configure. For example, to enable MD5 hashing and default output file

$ ./configure CFLAGS="-O2 -DDEFAULT_HASH_MD5 

The program can be statically linked by adding "-static" to the CFLAGS
compile options:

$ ./configure CFLAGS="-O2 -static"

Portability Notes:
Mac OS X:
To enable error recovery, use /dev/rdisk* instead of /dev/disk*

dc3dd can be compiled using Cygwin, but bad sectors can put the program
into an infinite loop due to bugs in Cygwin.

Please send all correspondence to: dc3dd@dc3.mil