Bug 552591

Summary:	Error unlocking LUKS device
Product:	[Fedora] Fedora	Reporter:	David Zeuthen <davidz>
Component:	cryptsetup-luks	Assignee:	LVM and device-mapper development team <lvm-team>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	agk, dwysocha, lvm-team, mbroz, mclasen, opensource, pjones, prockai, whulbert
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-05 16:20:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***