Bug 1045162 - VNC password not properly set in kickstart installation
Summary: VNC password not properly set in kickstart installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Shea
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1045119
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 18:45 UTC by David Shea
Modified: 2014-06-18 01:47 UTC (History)
8 users (show)

Fixed In Version: anaconda-19.31.43-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1045119
Environment:
Last Closed: 2014-06-13 10:55:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Shea 2013-12-19 18:45:18 UTC
This affects any password where the output of vncpasswd contains \r. "boring" is a good example.

+++ This bug was initially created as a clone of Bug #1045119 +++

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.

Comment 2 Tim Niemueller 2013-12-20 14:47:16 UTC
I'm a little confused, where does my password contain "\r"? I have specifically used dos2unix to rule this out as a possibility and I also tried 'vnc --password="boring"'. All with the same result. Is there something I can do to work around this problem for now?

Comment 3 David Shea 2013-12-20 14:55:08 UTC
(In reply to Tim Niemueller from comment #2)
> I'm a little confused, where does my password contain "\r"? I have
> specifically used dos2unix to rule this out as a possibility and I also
> tried 'vnc --password="boring"'. All with the same result. Is there
> something I can do to work around this problem for now?

The password itself doesn't contain \r. The problem is when we run the password through the vncpasswd command to generate the encrypted form that is used by the VNC server. The output of vncpasswd happens to contain \r, and anaconda was handling that incorrectly.

Comment 4 David Shea 2013-12-20 14:56:18 UTC
As far as workarounds for now: there isn't one, other than trying a different password.

Comment 6 Michal Kovarik 2014-01-30 15:43:09 UTC
Verified on RHEL-7.0-20140127.0 with anaconda-19.31.51-1.el7. I was able to connect with password to vnc when kickstart with 'vnc --password=boring' was used.

Comment 7 Ludek Smid 2014-06-13 10:55:32 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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