Ubuntu
cryptsetup package

  1. Bug #529502
  2. Comment #11

Comment 11 for bug 529502

Revision history for this message
ubuntuforum-bisi (ubuntuforum-bisi) wrote :

same issue, completely reproducible:
- from a cold boot (or any other starting condition)
- connect and power up external usb drive with encrypted LUKS volume in first partition
- use GUI or command line to unlock and mount volume
- use the volume for backup
- umount the encrypted volume
- attempt to lock (close) the encrypted block device

Encrypted data is still visible in nautilus, even though the mount table (mtab) no longer shows the presence of the device.

The difference: There is no way to lock/close the device.
manually running
/sbin/cryptsetup luksClose udisks-luks-uuid-...
yields:
Device udisks-luks-uuid-... is not active.
Device udisks-luks-uuid/... not found
depending on which UUID is used in place of the ellipsis

cryptsetup luksClose /sbin/cryptsetup luksClose /dev/disk/by-uuid/...
yields:
"Device ... is busy" message

the two UUIDs I'm working with:
/dev/sdc1: UUID="4e1a0099-6362-44a7-9435-3a87fb8add16" TYPE="crypto_LUKS"
/dev/mapper/external-mirror: UUID="a43905ea-0d70-4d5f-83e2-852ef930c0ad" TYPE="ext4"