Bug 500548

Summary: Mounting a LUKS encrypted device via GUI ignores keyfile defined in crypttab.
Product: [I don't know] kde Reporter: boernsen <xusmv15r>
Component: generalAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description boernsen 2025-02-21 20:07:34 UTC 
Mounting a LUKS encrypted device via GUI always shows password prompt despite keyfile definition in crypttab.

Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=412851
It's a different platform though and I though I should give more description.

STEPS TO REPRODUCE
1. Encrypt USB device with cryptsetup and add a keyfile to it
2. Add entry for device with keyfile in /etc/crypttab
3. Try to mount the device with cryptdisks_start / mount via terminal, then umount / cryptdisks_stop.
4. Try to mount the device via GUI (either via KDE dolphin or via task bar "Disks & Devices").

OBSERVED RESULT
Mounting via cryptdisks_start works without password prompt due to keyfile in crypttab.
Mounting via GUI shows password prompt, thus doesn't respect the keyfile defined in crypttab.

EXPECTED RESULT
Mounting via GUI uses keyfile defined in crypttab and omits the password prompt in that case.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 24.04
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1


ADDITIONAL INFORMATION
https://askubuntu.com/questions/1541875/how-to-unmount-an-encrypted-usb-via-gui-using-a-keyfile
Comment 1 boernsen 2025-02-22 14:34:31 UTC 
More detailed steps to reproduce can be found above at "additional information" (link to askubuntu.com)
Comment 2 boernsen 2025-02-23 16:51:09 UTC 
With Ubuntu Live 24.04.2 this problem doesn't exist, so I would say it must be a KDE specific problem or missing feature.
Comment 3 Nate Graham 2025-02-24 16:42:53 UTC 
Same thing, yeah.

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