File debian.control of Package dd_rescue

Source: ddrescue
Section: SystemUtilities
Priority: optional
Maintainer: Kurt Garloff <kurt@garloff.de>
Build-Depends: debhelper (>= 4.1.16), bc, libfallocate-dev, libattr1-dev, liblzo2-dev, openssl, libssl-dev, python

Package: ddrescue
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: dd_rescue is a data recovery and protection tool.
 When your disk has crashed and you try to copy it over to another one,
 standard Unix tools like cp, cat, and dd will abort on every I/O error,
 dd_rescue does not.
 It optimizes copying by using large blocks as long as no errors occur
 and falls back to smaller blocks. It supports reverse direction copying
 (to approach a bad spot from the top), sparse copying, preallocating
 space, splice zerocopy, and bypassing the kernel pagecache with O_DIRECT.
 dd_rescue provides safe deletion of data by overwriting files (or better
 partitions/disks) multiple times with fast random numbers.
 With the ddr_hash plugin, it supports calculating a hash value (such as
 a sha256sum) or an HMAC during copying.

Package: ddrescue-lzo
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: ddrescue (= ${binary:Version})
Description: The ddr_lzo plugin enables dd_rescue to de/compress data on
 the fly while it's copied with dd_rescue.
 ddr_lzo uses the lzo family of algorithms for this purpose. LZO is
 remarkably fast for decompression and still very fast when compressing
 at moderate compression levels. On the flipside, it does not compress
 as well as zlib. With the lzo1x family, ddr_lzo is compatible with lzop. 
 The plugin has a number of features to support data recovery in case
 .lzo files have been corrupted.

Package: ddrescue-crypt
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: ddrescue (= ${binary:Version})
Description: The ddr_crypt plugin enables dd_rescue to de/encrypt data on
 the fly while it's copied with dd_rescue.
 ddr_crypt uses the AES family of algorithms for this purpose. AES is
 considered safe by most cryptographers. It's fairly efficient to implement
 and some modern CPUs have hardware support for it. The x86 AES support
 is used by the plugin, ARMv8 is planned for the future.
 There are various numbers of bits and enhance number of rounds
 supported as well as various ways to handle and generate keys.