Bug 2460 - Kickstart encrypts an iscrypted password
Kickstart encrypts an iscrypted password
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-01 01:20 EDT by gordon.m.tetlow
Modified: 2016-09-19 15:10 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-05-28 19:51:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description gordon.m.tetlow 1999-05-01 01:20:33 EDT
When using kickstart to install a machine, I used an already
encrypted password. When it rebooted I couldn't log in as
root. After some investigating, I found out if I presented
the password hash I had specified in the kickstart file, it
would then let me log in.

In other words, during the install, the encrypted password
was encrypted again.
Comment 1 gordon.m.tetlow 1999-05-01 02:29:59 EDT
I checked the value of skipCrypt and found it to be 0 after the call
to poptGetContext inside of setRootPassword inside install2.c

This seems to be the problem, although why the poptGetContext is
returning skipCrypt as 0 is beyond me.

Gordon
Comment 2 David Lawrence 1999-05-10 15:52:59 EDT
I have verified this on a test lab machine.
Comment 3 David Lawrence 1999-05-10 15:54:59 EDT
*** Bug 2627 has been marked as a duplicate of this bug. ***


When doing a kickstart installation with RedHat 6.0
(kickstart is great!) and writing something like

rootpw --iscrypted 8d78LWoez74ef

in the kickstart file sets the root password to "8d78LWoe".
--iscrypted still worked in 5.2.  I quickly looked through
the code in install2, but there were little changes in
the password code, so I could not figure the problem out.
I have --useshadow in auth config.
Comment 4 Matt Wilson 1999-05-28 19:51:59 EDT
*** This bug has been marked as a duplicate of 2880 ***
Comment 5 Mike Smith 1999-06-16 19:51:59 EDT
This issue is not resolved....I have downloaded the updated
bootnet.img and it is still doing the same thing. It is crypting
the iscrypted text
Comment 6 osi 1999-06-17 04:13:59 EDT
Yep, I can confirm this as well.  The bootnet image dated
May 28th did not fix the problem.
Comment 7 openshift-github-bot 2016-09-19 15:10:04 EDT
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/47a2e769d1cd462d213f1367122e6af8c862650e
Merge pull request #2470 from abutcher/issue2460

[uninstall] Stop services on all hosts prior to removing files.

Note You need to log in before you can comment on or make changes to this bug.