** Original comment by rferris ** 1. Account name: Defence Signals Directorate Customer segment: 1 TAM/SRM customer: no VHT score: 4 Strategic Customer: yes 2. Ability to choose LUKS encryption type in Kickstart. 3. Customer is the Australian Department of Defence and requires aes-cbc-essiv:sa256 strength encryption on their storage devices. At this point in time Anaconda is hard coded to use only aes-xts-plain64, based on the outcome of BZ#600295 4. An option available in the kickstart configuration to set the LUKS encryption algorithm. 5. Customer sets and appropriate flag/option in kickstart configuration. After installation running the command below returns the algorithm selected algorithm. cryptsetup status luks-<id> 6. No 7. Sooner rather than later. 8. Yes 9. system-config-kickstart pykickstart anaconda 10. Yes
Follow-up patch (tested and) posted for review.
Verified on RHEL6.4-20121212.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0373.html