Bug 552591 - Error unlocking LUKS device
Summary: Error unlocking LUKS device
Keywords:
Status: CLOSED DUPLICATE of bug 539282
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptsetup-luks
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-05 16:03 UTC by David Zeuthen
Modified: 2013-03-06 04:00 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-05 16:20:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description David Zeuthen 2010-01-05 16:03:10 UTC 
I get an error when trying to unlock a LUKS device. It happens both in enforcing and permissive mode.

 cryptsetup-luks-1.1.0-0.5.fc13.x86_64
 device-mapper-1.02.40-2.fc13.x86_64
 libselinux-2.0.90-1.fc13.x86_64
 kernel-2.6.32.2-15.fc13.x86_64

 # cryptsetup luksOpen /dev/sdc1 lstuff
 Enter passphrase for /dev/sdc1: 
 /dev/mapper/temporary-cryptsetup-6451: lsetfilecon failed: No such file or directory
 /dev/mapper/temporary-cryptsetup-6451: open failed: No such file or directory
 Failed to open temporary keystore device.
 Failed to read from key storage.
Comment 1 David Zeuthen 2010-01-05 16:06:05 UTC 
I also get the same error when entering a wrong passphrase....
Comment 2 Milan Broz 2010-01-05 16:20:10 UTC 
This is not cryptsetup problem but some side effect of using udev in device-mapper backend, please see comments to bug 539282.

*** This bug has been marked as a duplicate of bug 539282 ***
Note You need to log in before you can comment on or make changes to this bug.