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):
# cryptsetup -c aes-xts-plain64 luksFormat /dev/vdb1 as an example
user is forced to use uppercase to type "yes" and if lowercase "yes" is typed, the command just silently exits without any helpful message.
both uppercase and lowercase "yes" should be accepted.
Also if user uses lowercase, command silently exits. We need to improve this usability.
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