Bug 678011
Summary: | cryptsetup luksOpen causes ** stack smashing detected *** for large key | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Milan Broz <mbroz> |
Component: | cryptsetup-luks | Assignee: | Milan Broz <mbroz> |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.6 | CC: | agk, atodorov, mbroz, prajnoha, prockai, pvrabec, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cryptsetup-luks-1.0.3-6.el5 | Doc Type: | Bug Fix |
Doc Text: |
Previously, the cryptsetup utility could have terminated unexpectedly when the key size was larger than 256 bits. The cryptsetup utility now properly supports keys longer than 256 bits, fixing the problem.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-07-21 07:04:16 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
Milan Broz
2011-02-16 13:49:43 UTC
Milan, can you explain what's the issue here and provide detailed steps to reproduce? Using large key (with some cipher supporting it) should be enough: # echo xxx | cryptsetup luksFormat -c blowfish-cbc-essiv:sha256 -s 448 /dev/sdb Command successful. # echo xxx | cryptsetup luksOpen /dev/sdb x key slot 0 unlocked. *** stack smashing detected ***: cryptsetup terminated Aborted (I did not yet analysed code, this bug is not present in upstream version.) What do you mean by large key? How large? see comment #2 I see now: --key-size, -s set key size in bits. Fixed in cryptsetup-luks-1.0.3-6.el5 Tested with cryptsetup-luks-1.0.3-8.el5: # losetup /dev/loop0 disk.img # echo xxx | cryptsetup luksFormat -c blowfish-cbc-essiv:sha256 -s 448 /dev/loop0 Command successful. # echo xxx | cryptsetup luksOpen /dev/loop0 x key slot 0 unlocked. Command successful. # ls -l /dev/mapper/x brw-rw---- 1 root disk 253, 2 May 10 06:00 /dev/mapper/x 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: Previously, the cryptsetup utility could have terminated unexpectedly when the key size was larger than 256 bits. The cryptsetup utility now properly supports keys longer than 256 bits, fixing the problem. 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 |