Bug 1415573 - cryptsetup forces users to use uppercase yes
Summary: cryptsetup forces users to use uppercase yes
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cryptsetup-luks
Version: 6.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-23 05:58 UTC by nikhil kshirsagar
Modified: 2019-12-16 07:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-01-23 09:41:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description nikhil kshirsagar 2017-01-23 05:58:20 UTC
Description of problem:
# cryptsetup -c aes-xts-plain64 luksFormat /dev/vdb1

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):

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

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