Red Hat Bugzilla – Bug 622712
cryptsetup hangs when isLuks is used on ordinary file
Last modified: 2013-02-28 23:09:06 EST
Description of problem:
Running cryptsetup isLuks on ordinary file causes cryptsetup to hang.
Version-Release number of selected component (if applicable):
RHEL 5.5 Server x86_64
Steps to Reproduce:
1. echo foo > /tmp/foo
2. cryptsetup isLuks /tmp/foo
crypsetup hang consuming 95% of CPU
Cannot read device /tmp/foo
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
# rpm -q cryptsetup-luks
# echo foo > /tmp/foo
# cryptsetup isLuks /tmp/foo
/tmp/foo is not a LUKS partition
# echo $?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The cryptsetup utility became unresponsive when using the "cryptsetup isLuks" command on an ordinary file. This problem has been fixed: if running the command on an ordinary file, the cryptsetup utility informs users about the file not being a LUKS partition.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.