Bug 50814

Summary:	mkkickstart doesn't write --enablemd5 in config file
Product:	[Retired] Red Hat Linux	Reporter:	Leonard den Ottolander <leonard-rh-bugzilla>
Component:	mkkickstart	Assignee:	Matt Wilson <msw>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-08-03 15:36:03 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 Leonard den Ottolander 2001-08-03 15:35:59 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Win98; U)

Description of problem:
mkkickstart doesn't write --enablemd5 in config file. Although bugreport 18235 says this is solved for RedHat 7.0 in rawhide, mkkickstart from 
RH 7.1 does *not* write --enablemd5 on a system with md5 encrypted passwords. Strange.

How reproducible:
Always

Steps to Reproduce:
1. mkkickstart > /etc/ks.cfg on a md5 passwords enabled system
2.
3.
	

Actual Results:  --enablemd5 flag is not written in the kickstart config file

Expected Results:  --enablemd5 flag written in the kickstart config file on systems with md5 encrypted passwords.

Additional info:

Comment 1 Matt Wilson 2001-09-10 16:26:17 UTC


*** This bug has been marked as a duplicate of 53073 ***

Comment 2 Leonard den Ottolander 2001-09-23 00:29:09 UTC

So the use of mkkickstart is discouraged. But ksconfig only works under X. Is 
there a command line tool to create ks.cfg files?

Comment 3 Matt Wilson 2001-09-24 19:07:37 UTC

the next version of red hat linux will create a kickstart config file after
every install.  Use that as the framework with a text editor to customize