[PATCH] accept symlinks to blockdevices for mount.crypt

Bug #6257 reported by hunger
4
Affects Status Importance Assigned to Milestone
libpam-mount (Debian)
Fix Released
Unknown
libpam-mount (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

Hi!

I just noticed that you need to pass a blockdevice to /usr/bin/mount.crypt. This is annoying since you can not use the cool new /dev/disk/by-whatever feature of udev that way.

Please use $( readlink -f "$1" ) when assigning DEVICE in that script. That way the device the link points to will be used and this will pass the is-this-a-blockdev test (which a symlink does not).

Thanks!

Regards,
Tobias

hunger (hunger)
Changed in libpam-mount:
assignee: nobody → pitti
Revision history for this message
hunger (hunger) wrote : patch

This is the patch for this.

Revision history for this message
Martin Pitt (pitti) wrote :

 libpam-mount (0.11.0-1ubuntu1) dapper; urgency=low
 .
   * Add debian/patches/26_cryptsetup_key_file.dpatch:
     - mount.crypt: Always read the passphrase from stdin.
     - Malone #6216.
   * Add debian/patches/27_mount.crypt_symlinks.dpatch:
     - mount.crypt: Resolve symbolic links for the device argument.
     - Malone #6257

Changed in libpam-mount:
status: Unconfirmed → Fix Released
Changed in libpam-mount:
status: Unknown → Unconfirmed
Changed in libpam-mount:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Patches

Remote bug watches

Bug watches keep track of this bug in other bug trackers.