[dm-crypt] [ANNOUNCE] cryptsetup 1.6.8

Milan Broz gmazyland at gmail.com
Tue Sep 8 13:21:44 CEST 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The stable cryptsetup 1.6.8 release is available at

    https://gitlab.com/cryptsetup/cryptsetup

Please note that release packages are located on kernel.org

    https://www.kernel.org/pub/linux/utils/cryptsetup/v1.6/

Feedback and bug reports are welcomed.

Cryptsetup 1.6.8 Release Notes
==============================

Changes since version 1.6.7

* If the null cipher (no encryption) is used, allow only empty password for LUKS.
  (Previously cryptsetup accepted any password in this case.)

  The null cipher can be used only for testing and it is used temporarily during
  offline encrypting not yet encrypted device (cryptsetup-reencrypt tool).

  Accepting only empty password prevents situation when someone adds another
  LUKS device using the same UUID (UUID of existing LUKS device) with faked
  header containing null cipher.
  This could force user to use different LUKS device (with no encryption)
  without noticing.
  (IOW it prevents situation when attacker intentionally forces
  user to boot into different system just by LUKS header manipulation.)

  Properly configured systems should have an additional integrity protection
  in place here (LUKS here provides only confidentiality) but it is better
  to not allow this situation in the first place.

  (For more info see QubesOS Security Bulletin QSB-019-2015.)

* Properly support stdin "-" handling for luksAddKey for both new and old
  keyfile parameters.

* If encrypted device is file-backed (it uses underlying loop device),
  cryptsetup resize will try to resize underlying loop device as well.
  (It can be used to grow up file-backed device in one step.)

* Cryptsetup now allows to use empty password through stdin pipe.
  (Intended only for testing in scripts.)

Cryptsetup API NOTE:

Direct terminal handling and password calling callback for passphrase
entry will be removed from libcryptsetup in next major (2.x) version
(application should handle it itself).
It means that application have to always provide password in API calls.

Functions returning last error will be removed in next major version (2.x).
These functions did not work properly for early initialization errors
and application can implement better function easily using own error callback.

See comments in libcryptsetup.h for more info about deprecated functions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV7sS/AAoJENmwV3vZPpj8qWUP/3B5thlnfFSCYoRxJkx6L3eH
tN9h5Y1ZQZ0bPigstVHk2yVvDkowvgDA1GR/LJMLQK4dXIbldC6cUZh8D0lAD48g
FnGg8ungrwvgfox3GML2Ml8P762DsMOwiBTRHLwZo+EpW+yYT5sv/Wi9vVCLNF5m
NXCP2UTl0tVxiLy8PVuklJjxEqy65UgSgThXDFiCdx230QIgHlo9Cc5tOWSaIvhz
UW5VrNtpms/ihHp4XK8cdCLxWw6HwGLvw5TGwifey56ToDyO+w+N72ttrCPh4edo
LsQC+z+zAV8n9KnwskSLNvRIF2bsjnbxNRaJWQ6BWr+jFjDqnYr/UJlz7pDOwgUA
Yiajaib2IZSA28+ydKw/aFARuRfRbSnEgVkooBSBbkk8SO6yFtAeJkSGvjxlupkO
WGkOmq5bKQ1J8Abz884BTZBM2crOvDSpuu/ISkBxvuXBpgad334K3ep/1OHNEbci
j8emNFUyR+OiQf3ptFBrmThk2pGxOseSElpfEK88ruAulHelPDupz7VUPPU/IJxn
Dx0f5zF4qtPKtHNpunRpA+apyj/xenwWjgIXB/1AUfQSBCAQeLB933DOqUN0cFnV
NLuoNQ2M+XU1+hLmC7/U7KLrAMeo1Bu52Tv8t5/HfHuHxjxRXEE5JAOowSGLg8fm
a/G2n6EZTL7ZXW+/cNe/
=4ZSC
-----END PGP SIGNATURE-----


More information about the dm-crypt mailing list