Bug 1045119 - VNC password not properly set in kickstart installation
Summary: VNC password not properly set in kickstart installation
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1045162
TreeView+ depends on / blocked
 
Reported: 2013-12-19 16:05 UTC by Tim Niemueller
Modified: 2014-02-28 13:54 UTC (History)
5 users (show)

Fixed In Version: anaconda-21.15-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1045162 (view as bug list)
Environment:
Last Closed: 2014-02-28 13:54:40 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.