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 cryptsetup-luks-1.0.3-5.el5 How reproducible: always Steps to Reproduce: 1. echo foo > /tmp/foo 2. cryptsetup isLuks /tmp/foo Actual results: crypsetup hang consuming 95% of CPU Expected results: Cannot read device /tmp/foo Additional info:
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.
Fixed in cryptsetup-luks-1.0.3-6.el5
# rpm -q cryptsetup-luks cryptsetup-luks-1.0.3-8.el5 # echo foo > /tmp/foo # cryptsetup isLuks /tmp/foo /tmp/foo is not a LUKS partition # echo $? 234 #
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. New Contents: 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. http://rhn.redhat.com/errata/RHBA-2011-0987.html