| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 06 Mar 2008 14:41:22 +0100
From: Matthias Koenig <mkoenig@...e.de>
To: Theodore Ts'o <tytso@....edu>
Cc: ludwig.nussel@...e.de, linux-ext4@...r.kernel.org
Subject: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices
Hi,
Current practice in defining crypto devices in common distributions
has:
1. A definition of the device-mapper name with the corresponding device
in /etc/crypttab
2. A definition in /etc/fstab for the mountpoint of the dm device.
Steps involved into setting up the crypto devices are
a. fsck local filesystems
b. mount local filesystems
c. device-mapper set up of crypto devices
d. fsck crypto filesystems
e. mount crypto filesystems
Steps a.+b. have to be done before the crypto device setup, because
the crypto device could be in a file container on a local filesystem.
Now, the problem appears if /etc/fstab contains a mount point of a
crypto device which is supposed to be fsck'd in step d. fsck will
fail in step a., since this device does not exist at this point in
the boot process (it will be set up in step c.)
In order to address this, I propose a new option for fsck, lets say '-X'.
Enabling this will skip a device-mapper device which is currently
nonexistent, but is defined in /etc/crypttab.
In this way crypto devices could be skipped without fsck failure when
running fsck -A.
Proposed patch to implement this below.
Regards,
Matthias
View attachment "e2fsprogs-1.40.7-ignore_crypto.patch" of type "text/x-patch" (3641 bytes)
Powered by blists - more mailing lists