Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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?
(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.
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.
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.