cryptsetup - disk encryption support - startup scripts

Distribution: Debian Sid
Repository: Debian Main i386
Package name: cryptsetup
Package version: 1.7.5
Package release: 1
Package architecture: i386
Package type: deb
Installed size: 359 B
Download size: 173.75 KB
Official Mirror:
Description: unavailable.



  • cryptsetup-luks


  • cryptsetup-luks


  • cryptsetup-luks
  • hashalot << 0.3-2


    Source package: cryptsetup

    Install Howto

    1. Update the package index:
      # sudo apt-get update
    2. Install cryptsetup deb package:
      # sudo apt-get install cryptsetup


    2017-09-14 - Guilhem Moulin <> cryptsetup (2:1.7.5-1) unstable; urgency=low * New upstream release 1.7.5. * cryptroot-unlock: When the standard input is a TTY, keep prompting for passphrases until there are no more devices to unlock. (Closes: #866786) * cryptsetup.prerm: Don't try to call `dmsetup table` to list dm-crypt devices when the dm_mod module isn't loaded. (Closes: #870673) * Rename upstream signing key from debian/upstream/signing-key.asc to debian/upstream-signing-key.asc in order to avoid lintian error orig-tarball-missing-upstream-signature" (we use the key to verify signature on upstrem's git tags). * Remove deprecated upstart configuration files: /etc/init/cryptdisks.conf and /etc/init/cryptdisks-udev.conf. Cf. `lintian-info --tags package-installs-deprecated-upstart-configuration`. * debian/cryptsetup.{postinst,postrm}: Don't hard-code path to update-initramfs(1). * debian/rules: Include /usr/share/dpkg/ to avoid parsing dpkg-parsechangelog(1) output. * debian/control: Bump Standards-Version to 4.0.0 (no changes necessary).

    2017-05-09 - Jonas Meurer <> cryptsetup (2:1.7.3-4) unstable; urgency=high [ Guilhem Moulin ] * Drop obsolete update-rc.d parameters. Thanks to Michael Biebl for the patch. (Closes: #847620) * debian/copyright: Fix license mismatch (docs/examples/* lib/crypto_backend/* lib/loopaes/* lib/tcrypt/* lib/verity/* python/* are LGPL-2.1+ not GPL-2+). (Closes: #861802) * debian/initramfs/cryptroot-hook: honor RESUME={none,auto} as documented in initramfs.conf(5) by initramfs-tools >=0.129. (Closes: #861074)

    2016-12-09 - Jonas Meurer <> cryptsetup (2:1.7.3-3) unstable; urgency=medium [ Jonas Meurer ] * debian/scripts/decrypt_ssl: fix script to actually output the decrypted key. Apparently this script has been broken since June 2008. Doesn't seem like anybody is using it. Thanks to g1 for spotting and reporting the error. (Closes: #844050) * debian/initramfs/cryptroot-script: + limit the sleep after max passphrase attempts to devices for the rootfs. This mitigates the negative impact in case of broken keyscripts etc. + add $crypttarget to each message to provide more context. * debian/initramfs/cryptroot-hook: fix sanity check for key files on root fs in get_device_opts(): detect if processed device is a root (parent) device even for LVM setups. (closes: #842951) * debian/README.initramfs: minor fix to the decrypt_derived keyscript section: now that systemd is standard, 'cryptdisks_start' should be used instead of '/etc/init.d/cryptdisks start'. * debian/manpages/crypttab.xml: add a warning to the 'keyscript' option that systemd doesn't support the option (yet) and mention the possible workaround to process the devices in question in the initramfs. [ Guilhem Moulin ] * add debian/gbp.conf to set the upstream tag to "v%(version%.%_)s". As this enables git-buildpackage >= 0.8.7 to automatically generate orig.tar.gz, step nr. 5 is now removed from debian/README.source. * debian/compat: bump debhelper compatibility version to 9. * debian/initramfs/cryptroot-hook: + fix tab damage for consistency with the rest of the code + better warning for deprecated settings + fix sanity check for key files in get_device_opts(): print a warning if the key file isn't on the root FS, or if the root device is not encrypted, even for LVM setups. + fix sanity check for key files in get_device_opts(): print a warning if the processed device is a resume device, even for LVM setups. + fix runtime error in get_lvm_deps() if the first argument is either missing or the empty string. + reset IFS after processing $rootopts in get_device_opts(); the missing linefeed in $IFS caused LVM logical volumes spaning over multiple PVs not to have their parent devices detected correctly.