Milan Broz dfa2755aba If the null cipher is used, allow only empty password for LUKS. ...

The cipher_null is no-encryption, it can be used for testing
or temporarily when encrypting device (cryptsetup-reencrypt).

Accepting only empty password prevents situation when you replace
a LUKS header on an unlocking device with the faked header using
null cipher (and the same UUID).
Here a system could think that the device was properly unlocked
(with any entered password) and will try to use this unencrypted
partition instead.
(IOW it prevents situation when attacker intentionaly forces
an user to boot into dirrerent 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 not allow this situation in the first place.
(Despite the fact that once you allow physical tampering of your system
it cannot be properly secured anymore.)

2015-07-02 08:21:19 +02:00

..

af.c

Change License from GPLv2 only to GPLv2+ ("or any later").

2012-12-29 11:33:54 +01:00

af.h

Change License from GPLv2 only to GPLv2+ ("or any later").

2012-12-29 11:33:54 +01:00

keyencryption.c

Fix keyslot device access for devices not supporting O_DIRECT.

2014-08-08 14:49:38 +02:00

keymanage.c

If the null cipher is used, allow only empty password for LUKS.

2015-07-02 08:21:19 +02:00

luks.h

Allow simple status of crypt device without providing metadata header.

2014-06-14 17:42:57 +02:00

Makefile.am

Fix buildsytem to always include config.h.

2013-06-23 17:14:33 +02:00