Bug 1852432

Summary:	user names with blank characters should not be allowed
Product:	Red Hat Enterprise Linux 8	Reporter:	Jiri Prajzner <jprajzne>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	jkoten, tpelka
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:	tigervnc-1.10.1-6.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 03:00:07 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 Jiri Prajzner 2020-06-30 12:19:59 UTC

Description of problem:
tvnc allows to use a user name that has a blank characer (e. g. a space) after it, leading to an error on vnc session start up.

Version-Release number of selected component (if applicable):
tigervnc-server-1.10.1-5.el8.s390x

How reproducible:
always

Steps to Reproduce:
1. edit /etc/tigervnc/vncserver.users with a user name tha thas a blank a character afer it: 'test ' for example
2. sudo systemctl start vncserver@:1
3. journal -xe

Actual results:
-- Unit vncserver@:1.service has begun starting up.
Jun 30 08:04:17 ibm-z-125.rhts.eng.bos.redhat.com vncsession-start[29877]: User "test " does not exist

Expected results:
vnc session up and running

Additional info:
i think it should generally strip the leading and trailing blank characters, same thing happens with leading space, e. g. ' :1=test'

Comment 1 Jan Grulich 2020-07-07 11:27:52 UTC

Fixed with tigervnc-1.10.1-6.el8.

Comment 4 Jiri Prajzner 2020-07-08 10:22:23 UTC

works nicely

Comment 7 errata-xmlrpc 2020-11-04 03:00:07 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (tigervnc bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4683