Back to Main page of KG

• dd_rescue does not provide character conversions.
• The command syntax is different. Call dd_rescue -h.
• dd_rescue does not abort on errors on the input file, unless you specify a maximum error number. Then dd_rescue will abort when this number is reached.
• dd_rescue does not truncate the output file, unless asked to.
• You can tell dd_rescue to start from the end of a file and move backwards.
• It uses two block sizes, a large (soft) block size and a small (hard) block size. In case of errors, the size falls back to the small one and is promoted again after a while without errors.

Purpose of dd_rescue

• Imagine, one of your partitions is crashed, and as there are some hard errors, you don't want to write to this hard disk any more. Just getting all the data off it and retiring it seems to be suitable. However, you can't access the files, as the file system is damaged.
• Now, you want to copy the whole partition into a file. You burn it on CD-Rom, just to never lose it again. You can setup a loop device, and repair (fsck) it and hopefully are able to mount it.
• Copying this partition with normal Un*x tools like cat or dd will fail, as those tools abort on error. dd_rescue instead will try to read and if it fails, it will go on with the next sectors. The output file naturally will have holes in it, of course. You can write a log file, to see, where all these errors are located.
• The data rate drops very low, when errors are encountered. If you interrupt the process of copying, you don't lose anything. You can just continue at any position later. The output file will just be filled in further and not truncated as with other Un*x tools.
• If you have one spot of bad sectors within the partition, it might be a good idea, to approach this spot from both sides. Reverse direction copy is your friend.
• The two block sizes are a performance optimization. Large block sizes result in superior performance, but in case of errors, you want to try to salvage every single sector. So hardbs is best be set to the hardware sector size (most often 512 bytes) and softbs to a large value, such as the default 16k.
• For automating data recovery, the script dd _rhelp is useful (and included in the binary builds).
  Meanwhile, the tool GNU ddrescue has been developed and provides an easier way for many data recovery scenarios than the combination of dd_rhelp and dd_rescue.
  dd_rescue on the other hand is still worthwhile because it has a number of special features, such as direct IO, sparse copies, splice copies, preallocation ...
  Noteworthy are the data protection functions that have been introduced since 1.29 to allow safe deletion of files and storage devices by overwriting with data from a fast userspace pseudo random number generator.
  In addition, since 1.42, there is a plugin interface that allows you to analyze or transform data. A (secure) hash calculation plugin exists as well as an LZO (de)compression plugin and an encryption. The plugins have a varying level of support for some of the special dd_rescue features, but where possible, they support things like reverse direction copy or sparse files (files with holes) etc. and you can store additional properties (such as a hash value or a salt) in extended attributes of the file.

I have also put the man pages for dd_rescue (1) and the ddr_crypt (1) and ddr_lzo (1) plugins online.

Just one note: It does work. I unfortunately did not just create this program for fun ...

Warning

History / News

Latest version is 1.99.17 (2024-11-02)
Improvements in version 1.99.17:

• New features:
  • libddr_lzma.so: De/Compression plugin to do LZMA2 (xz) compression. This was contributed by Dmitrii Ivanov. This allows us to cover the other end of the spectrum: High compression at high CPU cost for compression, which is the opposite of LZO, which has minimal CPU cost with moderate compression ratios. (Decompression is cheap on both.)
  • I did some cleanup to better align the code with how the rest of dd_rescue behaves and it took me some extra time to carefully review the plugin code before integrating it. This process is supposed to continue. More code review is welcome and looking how to ensure the code deals well with holes (sparse files) and with corruption of compressed data (as much as this is possible) is on the to do list. Help is very much welcome!

Latest version was 1.99.16 (2024-09-30)
Improvements in version 1.99.16:

• Build improvements:
  • Centralize CPU feature detection in archdep.
• Bugfixes:
  • Allow passing in password into crypt plugin via pipe and passfd=
• Improvements and optimization:
  • Optimized SHA2 (sha256/sha224) routines using CPU acceleration on x86-64 and armv8

Previous version 1.99.15 (2024-09-17)
Improvements in version 1.99.15:

• Build improvements:
  • Detect availability of pread64() and pwrite64() separately and replace individually. (Thanks David Geiger for reporting on Mageia.)
  • Automatically set -target linux-arm/aarch64-android28 if needed (Termux)
• Bugfixes:
  • printstatus() would not be called with odd offsets, resulting in missing progress report and missing sync (-y) and write throttling (-C).
• Improvements and optimization:
  • Some unrolling for the hash functions gives up to 10% better performance (on Zen4).
  • Rationalize prefetching for hash functions and clear memory after using (avoid cleartext data on the stack).
  • Save function calls for fault injection and for graph updates when unneeded.
  • Better handle progress update frequency.

Previous version was 1.99.14 (2024-08-22)
Improvements in version 1.99.14:

• Address a few issues around compilation on musl systems (e.g. Alpine):
• Detection of LFS64 functions by compiling not just library symbol search (linking)
• Include more headers to have all definitions, most notably fcntl.h
• More consistently define _LARGEFILE64_SOURCE and _GNU_SOURCE
• Thanks go to Erhard F., see sf issue #7
• Avoid lack of reasonable semantics of POSIX basename() by providing reasonable mybasename.h
• Prefetching of constants for hash functions
• Do more fuzzing in testing lzo, hoping in liblzo no longer accepting broken input, but problem on Fedora lblzo2 persists.
• Bugfix: Fix verbose output on fallback to small block sizes
• Bugfix: Consistently clear errno before new read attempts (broke on musl in specific scenarios)
• Bugfix: Avoid breakage on option -u without output file name
• Bugfix: Support openssl3, has a struct change of (private) struct _evp_cipher_ctx_st since 3.0.6, broke on 32bit systems. (Alignment rules hide it on 64bit.)
• Bugfix: On ARMv7, unaligned support test is not reliable, manually override

Version 1.99.13 (2023-02-24)
Improvements in version 1.99.13:

• Better optimization of aes.c
• Better fuzz testing of lzo
• Allow overriding strip binary (contributed by Anton Samsonov)
• ddr_hash: Support checksums reading/writing from stdin.stdout "-"
• Some -fanalyzer inspired improvements: Check for failed mem allocations
• Fix aliasing issue with XORN in aes (thanks Martin Liska, Jakub Jelinek)

Latest version is 1.99.12 (2022-07-26)
Version 1.99.12 has a few improvements:

• Works with openssl-3.0:
  • Using EVP_Cipher_Init() to set IV
  • Option nosalthdr to match missing Salted__ header
• ARMv7 fixes:
  • AES assembly works with clang now
  • Ensure we use bytewise access for potentially unaligned data
• Providing builds against Android API28 (Android 9+)

Version 1.99.11 (2021-04-29)
Version 1.99.11 has a few improvements:

• AES performance tuning:
  • Significant tuning of ARMv8 (and v7 on v8) crypto by better insn scheduling.
  • Extra tuning for ARMv8 CTR mode (full asm), significantly beating OpenSSL. (x2 encryption not done yet, let me know if this is important for you.)
  • Extra tuning for ARMv8 CBC mode (full asm), beating OpenSSL on decryption, slightly behind on encryption.
  • Minor improvements for AESNI (x86-64)
  • Support for 256bit VAES (Zen3, IceLake) for ECB and CTR. This required compiling aesni twice, once with and once without avx insn encoding (VEX).
  Results in impressive scores on AES128-ECB/-CTR scores (in cycles per byte): 0.23 (Zen3, VAES), 0.33 (Zen 3, AESNI), 0.40 (Cortex-A78), 0.66 (Haswell/Skylake).
• test_aes: Better parameter handling in test_aes.
• test_aes: Compare IV after encryption routines; ensure we always return the IV for the next (full) block.
• test_crypt.sh: Systematically test lengths 0 -- 130 bytes.
• Make OpenSSL AES wrappers safe against len=0.
• The fuzz_lzo program now reports when it can't tweak a compressed checksum due to the block being uncompressible. This allows retrying and avoiding a test case failure.

Version 1.99.10 (2021-03-08)
Version 1.99.10 has a few improvements:

• Resolve all warnings from deprecated autoconf usage.
• More precise arm64 crypto asm memory dependency statements.
• Significant speedup by optimizing insn scheduling and avoiding dependencies in AES CTR mode.
• Port arm64 crypto asm improvements and fixes also to arm32 (with ARMv8 crypto)

Version 1.99.9 (2021-02-27)
Version 1.99.9 has a few fixes:

• Newer systems have xattr.h included under sys/, so support xattrs also there.
• Newest compilers on Arm64 could miscompile the aes code due to aliasing issues and missing clobbers. This has been fixed. Thanks go to Dirk Müller.
• A few minor cleanups ensuring we free everything before exiting etc. and checking return values of all memory allocations.
• Quiesced a few warnings with -q
• One bugfix for handling filenames with spaces

Version 1.99.8 (2017-12-03)
Version 1.99.8 brings compatibility with OpenSSL-1.1. Trouble was that the EVP interface has significantly changed. Thanks got to Marcus Meissner for contributing the patch. I used the opportunity to structure the AES plugins a bit better; also the test_aes program now uses CPU detection and can thus be used in the check target.

Version 1.99.7 (2017-11-10)
Version 1.99.7 fixes a number of issues: The double/triple overwrite was broken due to the ratecontrol changes and has been fixed. (Thanks go to Egger Clemens for reporting and analyzing this one.) Testcase has been addded for it as well. Added openssl11 compatible Salted__ header using SHA256 hash for one-round KDF and document it. Some Makefile and test tweaks to survive strange environments, such as emulated PPC (which is slower than ratecontrol tests) and gentoo broken dash echo -n (sd ticket 3, thanks to "whissi".)
1.99.6 already has a few improvements for compilation (thanks go to Michael Matz). It also features multipart support in the hash module, so we can calculate and validate S3 style multipart checksums.

Version 1.99.5 (2016-12-29)
Version 1.99.5 has two compiler fixes and a better estimation (and thus better progress reporting) of the transfer length. It also has a new ratecontrol feature, allowing to throttle the speed with which data gets copied.

Version 1.99.4 (2016-08-25)
Version 1.99.4 has a couple of fixes on top of 1.99: A memory corruption was resolved when using fmt_int() improperly, which was the case when a list of bad blocks was written out with -b. Thanks to Marc Thomas for reporting and debugging. A segfault with the graph with reverse direction copies was also fixed as well as improved flexibility to compile ddr_crypt plugin with incomplete support for new insns.

Version 1.99 (2015-09-09)
Version 1.99 brings updates to the ddr_crypt plugin: It adds hardware acceleration for ARMv8 CPUs/SOCs (even if in 32bit mode) -- this is a 10x speedup on AES en/decryption operations. (An Cortex-A57 at 2.1GHz (Exy7420) does ~1GB/s with AES128-CTR.) The ddr_crypt plugin xattr support has been extended and it has an option to process openSSL compatible Salted__ files. A bug in CTR initialization has been fixed.
The main program sees improved write error retry logic and better fault injection logic (support for ranges, using absolute positions).
There are now more variants of Android binaries, see below in the i download section.

Version 1.98 (2015-05-30)
It has a few improvements such as a few cleanups, a fault injection framework for testing and significantly improved speed of the pseudo RNG. But the important feature is the addtion of a crypt plugin. You can insert it into the plugin chain to de/encrypt data using the AES family of algorithms. (More are planned for the future.) You can use 128/192/256 bit keys and optionally use a higher number of rounds to have an increased security margin. Keys (and IVs) can be generated, saved, retrieved or generated from password and salt. Please be aware that despite diligent testing this is a new plugin -- so be prepared that there will be some changes and bugfixes to it in the near future.

Sourceforge (2014-04-14)
The source code is in git on SourceForge now. It's actively developed, expect to see a 1.47 with an encryption plugin soon.

Version 1.46 (2014-08-09)
ddr_hash now supports calculating HMACS instead of plain hashes. The hash calculation has been cleaned up a bit. When a seed val of 0 is passed on the command line, additional randomness is created using the rdrand() command on x86/x86-64 (if available).
Note that I switched to creating .bz2 instead of .gz tarballs and using my new stronger GnuPG key 2bffc5bf instead of the old 1c98774e. This time, I offer the old .gz with old Gkey in addition, but I won't do this in the future.

(2014-06-27) A vulnerability in most implementations of lzo decompression has been reported. The liblzo2 library (up to and including v 2.06) used by the ddr_lzo plugin (until dd_rescue-1.45) is affected. You need i to feed specially crafted compressed data in blocks of 16MB or larger to the decompressor on 32bit platforms to exploit it, see the report for more details. (This issue has ID LMS-20140616-1/ CVE-2014-4607.)
The man page ddr_lzo advises to be careful when feeding data from untrusted sources to the decompressor; it seems that this advice has been wise. Fortunately, ddr_lzo does not normally feed such large blocks to the decompressor; you'd need to manually increase the soft block size to at least 8MB and ignore a warning to trigger this issue with dd_rescue. But it is possible.
So here's my advice:

• Update liblzo2 to 2.07 (or a fixed 2.06 version) which has this issue fixed (your Linux distributor should provide this very soon). This is enough to fix the issue, as the ddr_lzo plugin of dd_rescue does dynamically link against liblzo2, except for Android.
• If using my provided Android binaries, redownload and reinstall the libddr_lzo.so binary (now with version number 1.45a), which has been compiled against liblzo2.a v 2.07 or better use the binaries from 1.46.
• Be careful with media consumption -- ffmpeg/mplayer seems to be badly affected by this issue, even on 64bit platforms.

Version 1.45 (2014-05-27)
ddr_hash received a bugfix (sha512/sha384 could overflow a buffer). It gained support for sha1 hash. ddr_hash can now conveniently retrieve (and check) and store hashes in xattrs and md5sum/sha256sum/... style files. A new null plugin (ddr_null) was added.

Previous version was 1.44 (2014-05-23)
The plugin libddr_MD5.so (short ddr_MD5) has been renamed to ddr_hash, reflecting that we also support sha1, sha256, sha224, sha512, sha384 now. Checks have been added to the test suite and the documentation been updated accordingly.

Previous version was 1.43 (2014-05-20)
The main feature of 1.43 is the new lzo plugin. It de/compresses data using the lzo algorithms, which are very fast to decompress and most versions are also fast to compress (at somewhat moderate compression levels). The plugin supports many of dd_rescue's features, such as skipping bad blocks (encoding sparseness/holes into the output) as well as appending. It also continues on errors (skipping a whole block if nodiscard is NOT given) and allows to search for valid lzo block headers if sync is lost. fuzz testing has been done to support reliability. A man page ddr_lzo(1) has been created.
The plugin interface has been enhanced to support ddr_lzo; the MD5 plugin has also seen some work beyond just refactoring: It supports the parameter output/outfd= now and supports all type of holes that can be generated in a chain with ddr_lzo now.
Some minor improvements (docu, messages) and bug fixes have been applied. There also is a new ARMv8 (AArch64 aka ARM64) optimized routine to detect zero-blocks.

Version 1.42.1 (2014-03-06)
1.42.1 contains a fix for a sublety how we set up a handler for SIGILL and return with longjmp to detect the supported instruction sets of the CPU -- we need to manually reset the process' signal mask, otherwise a second failed probe would abort.

Version 1.42 (2014-03-03)
1.42 brings the possibility to load plugins to analyze or transform data before it's written to the output file(s). A plugin to calculate the MD5 hash is provided. posix_fadvise() is used if available (optimization) and dd_rescue now only provides a short usage info rather than the long help text on wrong parameters.

Version 1.41 (2014-02-25)
There has been a lot of internal refactoring that improves the detection of CPU features (at runtime) and libc/compiler features (at build time). One result is that this version supports building against the Android NDK. (armv7l binaries built against Android API 17 (aka 4.2) libc can be found below in the download section.) Another consequence is that AVX2 support is now enabled (for saving CPU cycles on sparse block detection). A few minor bugs have been addressed (the most serious one a harmless off-by-one on determining the size of a block device). Number formatting is more consistent now. There also a new option -u/--rmvtrim that deletes the created file again and issues a fstrim on the filesystem -- good if you filled the empty space of a filesystem with zeros for data protection and SSD refreshment.

Version 1.40.1 (2014-02-15)
It just has one patch to fix the SSE2 detection on i386 -- the old code would end in an endless loop ...

Version 1.40 (2013-08-18)
It brings copying of extended attributes (with -p/--preserve). It doubles the default soft block size for buffered IO, but brings sparse write optimization for half-empty blocks. It also optimizes copying by using the first write to get rid off odd file offsets. It also adds a lot more test cases to make check.

Previous version was 1.39 (2013-08-08)
It fixes an issue where a copied file could be appended zeros if hardblocksize copy was used (e.g. b/c hardbs==softbs, bnc #833765). There's also a bit better ARM asm optimization, yielding a ~15% performance increase. There's also a help/manpage clarification that syncfreq actually is a size. And we use autoconf now to determine the target system features. Default build target now uses libdl.

Previous version was 1.38 (2013-08-02); improving SSE sparse detection performance (by 40%), adding a testcase for the 1.35/1.36 bug and run it in make check. There's even an AVX version, but it's not enabled by default, as it's untested. --force/-f now allows to ignore a non-zero output position on non-seekable output and the curr.rate and ETA calculations have improved a bit.

Version 1.37 (2013-08-01) was fixing an issue with SSE2 sparse detection, which could spuriously detect zero-filled blocks and thus result in corrupted copies if option -a was used. (This would happen for blocks that had no bytes with the uppermost bit set, such as e.g. ASCII text.) Embarassing! Also fixed issues on big-endian machines (although these were inconsequential for dd_rescue).

Older version history ...

Roadmap

• Par2 module to add error correcting Reed-Solomon/Erasure Code
• Support for more de/compression algorithms in .lzo module
• More compressed file formats (.gz, .xz, lzip)
• More stream cipher modes (GCM, XTS) in crypt plugin.
• Keep track of successfully copied blocks in dd_rescue itself to ease dd_rhelp's job ...
• Some more optimization is possible on the hash implementations, especially for ARMv8.
• Addition of SHA-3 (and SKEIN?) algorithm to ddr_hash.
• Addition of a networking plugin, e.g. to do a simple S3 put/get.

Downloads

Note that the source code is available on the sourceforge git (DD_RESCUE_1_99_BRANCH) and can best be retrieved from there.

You can download

Version 1.99.17

• Source tar ball (1.99.17, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.16

• Source tar ball (1.99.16, bz2) and signature (new key)
• Patch for armv7 build (using .arch armv8-a instead of armv8)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.15

• Source tar ball (1.99.15, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.14

• Source tar ball (1.99.14, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.13

• Source tar ball (1.99.13, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.12

• Source tar ball (1.99.12, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)
• Android binaries (ARMv7, API28 => Android 9.0+ P, PIE)
• Android binaries (ARMv8(64bit), API28 => Android 9.0+ P, PIE)

Version 1.99.11

• Source tar ball (1.99.11, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)

Version 1.99.10

• Source tar ball (1.99.10, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)

Version 1.99.9

• Source tar ball (1.99.9, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.

Version 1.99.8

• Source tar ball (1.99.8, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.

Version 1.99.7

• Source tar ball (1.99.7, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)

Version 1.99.6

• Source tar ball (1.99.6, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.

Version 1.99.5

• Source tar ball (1.99.5, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)

A note on the binaries for Android above: You only really need dd_rescue and libddr_*.so plugins (and the ddr_MD5 plugin is a symlink to ddr_hash), the rest are test programs. Choose the right ones, download and put them in a directory in your search $PATH (/system/xbin on rooted phones, the ones from your terminal emulator or sshd otherwise). Make them executable (chmod 0755). Best refer to the plugins using the full filenames or append the directory in LD_LIBRARY_PATH.

Version 1.99.4

• Source tar ball (1.99, bz2) and signature (new key) and the patch to 1.99.4 with signature
• Find binaries on open BuildService for various distributions and architectures.
• Android binaries (ARMv5/v7, API9 => Android 2.3.4+ GB)
• Android binaries (ARMv7, API16 => Android 4.1+ JB, PIE)
• Android binaries (ARMv8(64bit), API21 => Android 5.0+ L, PIE)

A note on the binaries for Android above: You only really need dd_rescue and libddr_*.so plugins (and the ddr_MD5 plugin is a symlink to ddr_hash), the rest are test programs. Choose the right ones, download and put them in a directory in your search $PATH (/system/xbin on rooted phones, the ones from your terminal emulator or sshd otherwise). Make them executable (chmod 0755). Best refer to the plugins using the full filenames or append the directory in LD_LIBRARY_PATH.

Version 1.98

• Source tar ball (1.98, bz2) and signature (new key)
• Find binaries on open BuildService for various distributions and architectures.
• dd_rescue Android (armv7l) binary (and signature) and the libddr_null.so plugin with signature and the libddr_hash.so plugin with signature and the libddr_lzo.so plugin with signature and the libddr_crypt.so plugin with signature.

Version 1.46

• Source tar ball (1.46, bz2) and signature (new key)
• Source tar ball (1.46, gz) and signature (old key)
• Find binaries on open BuildService
• dd_rescue Android (armv7l) binary (and signature) and the libddr_null.so plugin with signature and the libddr_hash.so plugin with signature and the libddr_lzo.so plugin with signature.

Version 1.45

• Source tar ball (1.45) and signature
• Find binaries on open BuildService
• dd_rescue Android (armv7l) binary (and signature) and the libddr_null.so plugin with signature and the libddr_hash.so plugin with signature and the libddr_lzo.so plugin with signature.

Version 1.44

• Source tar ball (1.44) and signature
• Find binaries on open BuildService
• dd_rescue Android (armv7l) binary (and signature) and the libddr_hash.so plugin with signature and the libddr_lzo.so plugin with signature.

Version 1.43

• Patch from 1.43 to 1.43.1, adds a warning to the lzo plugin, documents the 256kiB limit of lzop in the ddr_lzo(1) man page and adjusts the test suite to avoid blocks larger than 256kiB.
• Source tar ball (1.43) and signature
• Find binaries on open BuildService
• dd_rescue Android (armv7l) binary (and signature) and the libddr_MD5.so plugin with signature and the libddr_lzo.so plugin with signature.

Version 1.42.1

• Source tar ball (1.42.1) and signature
• Find binaries on openSUSE BuildService
• For Android, use the 1.42 binaries below -- they are unaffected by the signal handling used for instruction set probing that 1.42.1 fixes.

Version 1.42

• Source tar ball (1.42) and signature
• Find binaries on openSUSE BuildService
• dd_rescue Android (armv7l) binary (and signature) and the libddr_MD5.so plugin with signature.

Version 1.41

• Source tar ball (1.41) and signature
• Find binaries on openSUSE BuildService
• dd_rescue Android (armv7l) binary (and signature).

Version 1.40.1

• Source tar ball (1.40.1) and signature
• Find binaries on openSUSE BuildService

Version 1.40

• Source tar ball (1.40)
• Find binaries on openSUSE BuildService

Version 1.39

• Source tar ball (1.39)
• Find binaries on openSUSE BuildService

Version 1.38

• Source tar ball (1.38)
• Find binaries on openSUSE BuildService

Version 1.37

• Source tar ball (1.37)
• Find binaries on openSUSE BuildService

Version 1.36

• Source tar ball (1.36)
• Find binaries on openSUSE BuildService

Version 1.35

• Source tar ball (1.35)
• Find binaries on openSUSE BuildService

Version 1.34

• Source tar ball (1.34)
• Find binaries on openSUSE BuildService

Version 1.33

• Source tar ball (1.33)
• Find binaries on openSUSE BuildService

Version 1.32

• Source tar ball (1.32)
• Find binaries on openSUSE BuildService

Version 1.31

• Source tar ball (1.31)
• Find binaries on openSUSE BuildService

Version 1.30

• Source tar ball (1.30)
• Find binaries on openSUSE BuildService

Version 1.29

• Source tar ball (1.29)
• Find binaries on openSUSE BuildService

Version 1.28

• Source tar ball (1.28)
• Find binaries on openSUSE BuildService

Version 1.27

• Source tar ball (1.27)
• Find binaries on openSUSE BuildService

Version 1.25

• Source tar ball (1.25)
• Find binaries on openSUSE BuildService

Version 1.24

• Source tar ball (1.24)
• Find binaries on openSUSE BuildService

Version 1.23

• Source tar ball (1.23)
• Find binaries on openSUSE BuildService

Version 1.22

• Source tar ball (1.22)
• Find binaries on openSUSE BuildService

Version 1.21

• Source tar ball (1.21)
• Find binaries on openSUSE BuildService

Version 1.20

• Source tar ball (1.20)
• Find binaries on openSUSE BuildService

Version 1.18

• Source tar ball (1.18)
• Find binaries on openSUSE BuildService

Version 1.15

• Source tar ball (1.15)
• Find binaries on openSUSE BuildService

Version 1.14

• Source tar ball (1.14)
• Find binaries on openSUSE BuildService

Version 1.13

• Source tar ball (1.13)
• Find binaries on openSUSE BuildService

Version 1.12

• Source tar ball (1.12)
• Source RPM (1.12)
• Binary i586 RPM (1.12 for SuSE Linux 9.1 +)
• Binary x86-64 RPM (1.12 for SuSE Linux 9.1 +)

Version 1.11

• Source tar ball (1.11)

Older versions

• Source tar ball (1.10)
• Source tar ball (1.04)
• Source tar ball (1.03)
• Source tar ball (1.02)
• Source tar ball (1.01)

Copyright