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.
Bug 679224 - installer overwrites all new device passphrases with first-specified/global passphrase
Summary: installer overwrites all new device passphrases with first-specified/global p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 679223
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-21 23:08 UTC by David Lehman
Modified: 2011-05-19 12:38 UTC (History)
3 users (show)

Fixed In Version: anaconda-13.21.100-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 679223
Environment:
Last Closed: 2011-05-19 12:38:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0530 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-05-18 17:44:52 UTC

Description David Lehman 2011-02-21 23:08:19 UTC 
+++ This bug was initially created as a clone of Bug #679223 +++

+++ This bug was initially created as a clone of Bug #679166 +++

Description of problem:
Documentation for kickstart configuration for partitions says there is a --passphrase parameter to specify each partition's passphrase.
However after installation all partitions are mounted with the same passphrase as if it was a global default

Version-Release number of selected component (if applicable):
pykickstart 1.77-2
anaconda 13.22-1

How reproducible:

always

Steps to Reproduce:
1. Create a kickstart configuration file with a set of partitions where at least two are encrypted and define a different passphrase
2. make an unattended installation with said kickstart

  
Actual results:
At boot, there is a password prompt for mounting a partition. If entered correctly, all partitions are mounted and boot process continiues.

Expected results:
It should be needed to enter all passphrases in order to continue.


Additional info:

--- Additional comment from tsukebumi on 2011-02-21 14:26:18 EST ---

Created attachment 479981 [details]
example kickstart file

--- Additional comment from clumens on 2011-02-21 16:46:59 EST ---

*** Bug 679165 has been marked as a duplicate of this bug. ***

--- Additional comment from dlehman on 2011-02-21 17:50:31 EST ---

Created attachment 480014 [details]
f14 updates to not overwrite passphrases with first/global passphrase

Place the attached updates.img file in os/images/ in your install directory to get it picked up and used automatically. We don't do official fixes for the installer for Fedora 14 after the initial release, but this updates image should fix the problem you have seen.

Let me know if this doesn't solve your problem.

--- Additional comment from dlehman on 2011-02-21 18:07:12 EST ---

If a user creates multiple encrypted devices in kickstart, the first passphrase we find becomes the default/global passphrase in case any other encrypted devices have no passphrase specified. We are erroneously overwriting all devices' passphrases with the global/default when we should only be apply the default to those devices for which no passphrase has been set.

Similarly, if multiple encrypted devices are created in the GUI and a global passphrase is established by the user after having specified passphrases for some newly encrypted devices we should only use the global passphrase for that and subsequent devices instead of overwriting the passphrases already established for previously-created devices.
Comment 3 tsukebumi 2011-02-22 22:07:10 UTC 
I put the file on the nfs server used by the kickstart. (os/images/updates.img)
It didn't work out.

I am wondering if I missed something, or if the file must go on the installation media, in which case how to get it there.
I used pungi to generate the install cd.
Comment 4 RHEL Program Management 2011-02-22 22:19:54 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 6 Pavel Holica 2011-03-07 14:35:47 UTC 
Reproduced on RHEL 6.0 x86_64 Server GA.
Verified on RHEL6.1-20110224.2 x86_64 Server.

Different passwords are now set on different partitions created via kickstart.
Comment 7 errata-xmlrpc 2011-05-19 12:38:17 UTC 
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-0530.html
Note You need to log in before you can comment on or make changes to this bug.