Bug 895066

Summary:	vlock doesn't accept root password
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Bokoc <pbokoc>
Component:	vlock	Assignee:	Karel Zak <kzak>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	bnater, dsboger
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	When a user password is used to lock a console with vlock, the console can only be unlocked with the user password, not the root password. That is, even if the first inserted password is incorrect, and the user is prompted to provide the root password, entering the root password fails with an error message.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:42:25 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 Petr Bokoc 2013-01-14 13:06:42 UTC

Description of problem:
vlock doesn't unlock the console with root password, only user password

Version-Release number of selected component (if applicable):
vlock-1.3-31.el6

How reproducible:


Steps to Reproduce:
1. lock a console using vlock as an user
2. when prompted, enter wrong or blank user's password
3. vlock then asks for root password, enter the correct one
  
Actual results:
console stays locked, vlock outputs a "wrong password" message

Expected results:
console should be unlocked

Additional info:
- if you use vlock when logged in as root, it asks for the root password twice. In this case it works, vlock accepts the second password even if the first one was incorrect.

- the same problem exists on fedora 17: vlock-1.3-31.fc17

Comment 2 Davi 2013-04-10 01:19:54 UTC

The same problem exists in Fedora 18 (vlock-1.3-33.fc18)

Comment 3 RHEL Program Management 2013-10-14 00:05:20 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Jan Kurik 2017-12-06 10:42:25 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/