Bug 1301682

Summary:	katello-configure doesn't ave answer file "Default-answer-file" documented
Product:	Red Hat Satellite	Reporter:	Kurt Seifried <kseifried>
Component:	Docs Install Guide	Assignee:	Allison Heslin <aheslin>
Status:	CLOSED NOTABUG	QA Contact:	Russell Dickenson <rdickens>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Unspecified	CC:	adahms, kseifried
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 17:14:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kurt Seifried 2016-01-25 16:52:25 UTC

When using katello-configure it is possible to use an answer file "Default-answer-file"  to pass options, this is supported but not documented. This is a problem because users can password passwords as command line options, which an attacker may see (by running ps for example). The safer alternative is for a user to use an answer file, so the password is not exposed. If the  "Default-answer-file"  answer file can be documented I would appreciate that, thanks!

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 1 Andrew Dahms 2016-07-28 10:49:03 UTC

Assigning to Ali for review.

Comment 2 Allison Heslin 2016-08-03 13:25:15 UTC

Hi Kurt,

It looks like we document the answer file here: 

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide#performing_initial_configuration_sat_server_answerfile

Does that sufficiently meet your request?

Comment 3 Kurt Seifried 2016-08-04 00:34:14 UTC

Ah ok, it wasn't in the man pages and no mention of passwords/etc occurred in the docs. Maybe it could be improved to make it easier to find.

Comment 4 Allison Heslin 2016-08-04 17:14:02 UTC

We're working on improving the structure of the guide for the next release. Since the content is there, I think it's ok to close this one since it'll be covered by that effort.