linux-ext4 - Re: Patch to support LUKS UUIDs in libblkid

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <46A4C272.3040907@redhat.com>
Date:	Mon, 23 Jul 2007 17:00:02 +0200
From:	Karsten Hopp <karsten@...hat.com>
To:	Theodore Tso <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: Patch to support LUKS UUIDs in libblkid

Theodore Tso schrieb:
> Thanks, I've applied the blkid LUKS patch to the e2fsprogs SCM (modulo
> a minor whitespace breakage which I fixed up).
>

  I've encountered a problem with this patch, consider the following
  setup:

  in /etc/fstab:
  UUID=<some LUKS uuid>  / ext3 defaults 0 0

  During bootup the init scripts run 'fsck -A', fsck reads in /etc/fstab and
  converts the LUKS-uuid to a device name. It then uses this devicename to
  populate filesys_info and sets the type to ext3 (from fstab). It then tries to check
  the underlying device instead of the /dev/mapper/ LUKS device.

  I'm not sure how to work around this, adding crypt_luks to ignored_types won't work
  because fsck thinks the device has an ext3 FS.
  Is create_fs_device() the right place to add a check if this is a LUKS device or would it be better
  to do that in parse_fstab_line() around the blkid_get_devname() call ?

  Karsten

--
  Karsten Hopp        | Mail: karsten@...hat.de
  Red Hat Deutschland | Tel: +49-711-96437-0
  Hauptstaetterstr.58 | Fax: +49-711-613590
  D-70178 Stuttgart   | http://www.redhat.de
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html