Bug 1415573

Summary:	cryptsetup forces users to use uppercase yes
Product:	Red Hat Enterprise Linux 6	Reporter:	nikhil kshirsagar <nkshirsa>
Component:	cryptsetup-luks	Assignee:	LVM and device-mapper development team <lvm-team>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8	CC:	agk, mbroz, okozina, prajnoha, prockai, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-23 09:41:42 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 nikhil kshirsagar 2017-01-23 05:58:20 UTC

Description of problem:
# cryptsetup -c aes-xts-plain64 luksFormat /dev/vdb1

WARNING!
========
This will overwrite data on /dev/vdb1 irrevocably.

Are you sure? (Type uppercase yes):    <<========== why do we force users to use uppercase?
Enter LUKS passphrase: 
:


Version-Release number of selected component (if applicable):
cryptsetup-luks-1.2.0-11.el6.x86_64

How reproducible:
# cryptsetup -c aes-xts-plain64 luksFormat /dev/vdb1 as an example


Actual results:
user is forced to use uppercase to type "yes" and if lowercase "yes" is typed, the command just silently exits without any helpful message. 

Expected results:
both uppercase and lowercase "yes" should be accepted.

Additional info:

Also if user uses lowercase, command silently exits. We need to improve this usability.

Comment 4 Ondrej Kozina 2017-01-23 09:41:42 UTC

The utility returns error code and user is clearly asked it should be upper case. If those interactive prompts (double confirmations) are annoying there's -q/--batch-mode to suppress those prompts completely