Bug 363066 - Luks dm-crypt encrypted disks and ROM media cannot be ejected via the filemanager
Summary: Luks dm-crypt encrypted disks and ROM media cannot be ejected via the fileman...
Status: RESOLVED DUPLICATE of bug 245944
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-14 12:18 UTC by Frank
Modified: 2017-08-18 18:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank 2016-05-14 12:18:06 UTC
Version 16.03.90

I use encrypted BR-Ds and dolphin detects them and mounts / decrypts them. Fine. But if one after that tries to unmount them the cryptsetup binding stays in place and they cannot be ejected unless one does a manual cryptsetup close on the automounted device.

It should not only unmount the device but also detach the cryptsetup device mapping!

Reproducible: Always

Steps to Reproduce:
1. Put in BR-D with Luks dm-crypted iso
2. open it with dolphin which asks for password and mounts it
3. Try to unmount / release / eject it via dolphin

Actual Results:  
the cryptsetup binding stays in place and they cannot be ejected unless one does a manual cryptsetup close on the automounted device.

Expected Results:  
It should not only unmount the device but also detach the cryptsetup device mapping!

It is nice that dolphin supports encrypted devices, but so far the support is "half-assed". People without a deep knowledge of the underlying encryption process will not be able to manually detach the device to eject the media.
Comment 1 Nate Graham 2017-08-18 18:30:31 UTC
Yeah, it's definitely a bit half-baked. I'm going to mark this as a duplicate of the general "LUKS container support" bug so that we can centralize information and effort there.

*** This bug has been marked as a duplicate of bug 245944 ***