Bug 1045119

Summary:	VNC password not properly set in kickstart installation
Product:	[Fedora] Fedora	Reporter:	Tim Niemueller <tim>
Component:	anaconda	Assignee:	David Shea <dshea>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	anaconda-maint-list, dshea, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-21.15-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1045162 (view as bug list)		Environment:
Last Closed:	2014-02-28 13:54:40 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:
Bug Depends On:
Bug Blocks:	1045162

Description Tim Niemueller 2013-12-19 16:05:49 UTC

Description of problem:
When using the VNC option for a kickstart installation the password is not properly set.

Version-Release number of selected component (if applicable):
anaconda-20.25.15-1.fc20.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1. Have something like this in your ks.cfg:
vnc --password=boring
2. Try to login via VNC during installation

Actual results:
VNC access is denied.

Expected results:
Access granted with the given password.

Additional info:
In case of the "boring" password the file is 9 bytes long, instead of 8 bytes when setting it manually. Changing to the second screen shell and setting the password manually during installation with "vncpasswd /tmp/vncpassword" with the very same password makes the login work.