BTS

Message4720

Author mika
Recipients
Date 2014-02-10.11:56:16
Content
The luks-enabled persistency doesn't seem to work (or its usage is unclear :)).

Also it emmits strange error message during bootup because it tries to access
/tmp/custom_mounts.list before making sure file exists (also see attached
screenshot).

How to reproduce (rewriting from memory):

* cryptsetup luksFormat /dev/sdX2
* cryptsetup luksOpen /dev/sdX2 crypto
* mkfs.ext4 -L persluks /dev/mapper/crypto
* mount /dev/mapper/crypto /media/test
* echo "union /" > /media/test/persistence.conf
* umount /media/test
* cryptsetup luksClose /dev/mapper/crypto
* reboot with boot options "persistence persistence-encryption=luks
persistence-label=persluks"
History
Date User Action Args
2014-02-10 11:56:16mikasetmessageid: <1392033376.98.0.513712711094.issue1292@bts.grml.org>
2014-02-10 11:56:16mikalinkissue1292 messages
2014-02-10 11:56:16mikacreate