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.
Bug 1415573 - cryptsetup forces users to use uppercase yes
Summary: cryptsetup forces users to use uppercase yes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cryptsetup-luks
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
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:
Environment:
Last Closed: 2017-01-23 09:41:42 UTC
Target Upstream Version:
Embargoed:

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

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
Note You need to log in before you can comment on or make changes to this bug.