Package: ddrescue Version: 1.99-0.3.0-0.17.3 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 309 Depends: libc6 (>= 2.34) Filename: amd64/ddrescue_1.99-0.3.0-0.17.3_amd64.deb Size: 124236 MD5sum: 1be56c2c521acab3c984eb7c43bca3d5 SHA1: 6861cce4a0c7835f221147e1dfbfc71fa3fd35fe SHA256: 1aa5874954c1019d3e4ebf2a30faae540dc9150dfb589364df69316b31724cbc Section: SystemUtilities Priority: optional 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-crypt Source: ddrescue Version: 1.99-0.3.0-0.17.3 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 231 Depends: libc6 (>= 2.25), libssl3 (>= 3.0.0~~alpha1) Recommends: ddrescue (= 1.99-0.3.0-0.17.3) Filename: amd64/ddrescue-crypt_1.99-0.3.0-0.17.3_amd64.deb Size: 82344 MD5sum: 050769f565a7c3f83f8a66664a55552d SHA1: 95f4a5ff1441434799faa4acb6ce7535cd25e24b SHA256: a922cc4a0bc1822b219c1c960304f6b4473c411ce7b485ae86164d2437d51434 Section: SystemUtilities Priority: optional 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. Package: ddrescue-lzma Source: ddrescue Version: 1.99-0.3.0-0.17.3 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 39 Depends: libc6 (>= 2.14), liblzma5 (>= 5.1.1alpha+20120614) Recommends: ddrescue (= 1.99-0.3.0-0.17.3) Filename: amd64/ddrescue-lzma_1.99-0.3.0-0.17.3_amd64.deb Size: 16342 MD5sum: 691e933212ee0ee25573ae60488ebac9 SHA1: 5b792f67feca3f25c512b1f2624bef7c63aa7d25 SHA256: bc56c1e87c170fce75060c0acadec87db5b88ab209444ab95e063e35fdf55d38 Section: SystemUtilities Priority: optional Description: The ddr_lzma plugin enables dd_rescue to de/compress data on the fly while it's copied with dd_rescue. ddr_lzma uses the lzma algorithm which is used by xz. LZMA is slow on compression, but achieved very high compression ratios. Decompression is fast. The plugin is new and may not work well with corrupt or malicious data. Package: ddrescue-lzo Source: ddrescue Version: 1.99-0.3.0-0.17.3 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 71 Depends: libc6 (>= 2.33), liblzo2-2 (>= 2.02) Recommends: ddrescue (= 1.99-0.3.0-0.17.3) Filename: amd64/ddrescue-lzo_1.99-0.3.0-0.17.3_amd64.deb Size: 27306 MD5sum: 901fc887ead2a9895b010bd9bd88e43e SHA1: 94e5425ee4e09352072c5715d360fac716ffc225 SHA256: d0b1dac22c1be40f5e2c84612cadee8297d1b1d0d3cd70a092b43117db995271 Section: SystemUtilities Priority: optional 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: libfallocate-dev Source: libfallocate Version: 0.1.1-2 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 21 Recommends: libfallocate0 (= 0.1.1-2) Filename: amd64/libfallocate-dev_0.1.1-2_amd64.deb Size: 4202 MD5sum: 7b702c622bcdcd17f06d1e87294c6ea9 SHA1: 8fbec3f8115f318ba78f5616529f93853468cb09 SHA256: c0a3cb2d9d887ec79fc97b9bd7dfa7dbc3c4aade7ce6f70a940d6d38d7ad599f Section: SystemLibraries Priority: optional Description: libfallocate provides an interface for applications to tell filesystems about the size of to-be-written files, so the filesystem can do a better job in taking allocation decisions to avoid fragmentation. This package contains the header files needed for development as well as the static library. Package: libfallocate0 Source: libfallocate Version: 0.1.1-2 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 32 Depends: libc6 (>= 2.33) Filename: amd64/libfallocate0_0.1.1-2_amd64.deb Size: 7354 MD5sum: 23ea3f462d6f00d8caadb099f749cc8d SHA1: 113936f5e49cacba0743241de156ae756642d7a1 SHA256: fc3baf0d276509e8b217f046083c1b0193687c0fa8cb24a9570394b92dbb374f Section: SystemLibraries Priority: optional Description: libfallocate provides an interface for applications to tell filesystems about the size of to-be-written files, so the filesystem can do a better job in taking allocation decisions to avoid fragmentation. libfallocate provides a wrapper for the fallocate() syscall in case your glibc (<2.10) does not have it yet. It also provides linux_fallocate() which will attempt the space reservation ioctl that xfs and ocfs2 provide in case fallocate() did not succeed. It has an additional richer interface fallocate_with_fallback() that allows you to instruct it to fallback to do preallocation by zeroing things out (like posix_fallocate()) or to extend the file size by a sparse write (like a successful fallocate() with mode==0 would have done). Package: libs3-4 Source: libs3 Version: 4.1-5 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 184 Depends: libc6 (>= 2.34), libcurl4 (>= 7.16.2), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4) Filename: amd64/libs3-4_4.1-5_amd64.deb Size: 63898 MD5sum: f59f6f53875e4b29d4c994b96e801676 SHA1: cd96cabd7872bc9b5b170ccbee1ecbaa864a2557 SHA256: a444b0f19d505e7636ad9f7b5106b30ec5057178568fa9103bfcc69ccf298a58 Section: SystemUtilities Priority: extra Homepage: http://sourceforge.net/projects/reallibs3 Description: This package includes the libs3 shared object library, needed to run applications compiled against libs3, and additionally contains the s3 utility for accessing Amazon S3. Package: libs3-dev Source: libs3 Version: 4.1-5 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 279 Recommends: libs3-4 (= 4.1-5) Filename: amd64/libs3-dev_4.1-5_amd64.deb Size: 60434 MD5sum: 4261f67d075f34b9163f6e5b9e4730bd SHA1: e23fa280570145d7abd4bf926eedc2d948b43a00 SHA256: 0d4fa6549733b9916bdcd2175926bcb81f2d9f43c5382d9732d0341dc20481b8 Section: SystemUtilities Priority: extra Homepage: http://sourceforge.net/projects/reallibs3 Description: This library provides an API for using Amazon's S3 service (see http://s3.amazonaws.com). Its design goals are: - To provide a simple and straightforward API for accessing all of S3's functionality - To not require the developer using libs3 to need to know anything about: - HTTP - XML - SSL In other words, this API is meant to stand on its own, without requiring any implicit knowledge of how S3 services are accessed using HTTP protocols. - To be usable from multithreaded code - To be usable by code which wants to process multiple S3 requests simultaneously from a single thread - To be usable in the simple, straightforward way using sequentialized blocking requests Package: otc-tools Version: 0.8.34-3+6.1 Architecture: amd64 Maintainer: Kurt Garloff Installed-Size: 326 Depends: jq Recommends: libs3-4 Filename: amd64/otc-tools_0.8.34-3+6.1_amd64.deb Size: 74856 MD5sum: a75ffd4aa0d05f27b8ef76fde54a9f4c SHA1: 38c1a017067de6b2aa205d77d9617e16f3ef0fdf SHA256: 6880cb5c84ae904e2925a8800f1ef1548fe123258b48bbf21b548ec84c388a77 Section: SystemUtilities Priority: optional Description: This is a shell script that uses curl and jq to talk to the Open Telekom Cloud APIs (OpenStack and OTC specific APIs). It's a nice demonstrator to see how the API works and allows for simple automation and testing. For production use, we recommend the native python-openstackclient, amended with -otcextensions. Authors: Zsolt Nagy and Kurt Garloff