Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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