luksFormat should complain if entry is not in UPPERCASE

[GoogleCodeExporter]

What steps will reproduce the problem?
1. launch luksFormat /dev/vda7
2. type 'yes'

What is the expected output? What do you see instead?
I would like the utility to complain that the entry is bogus. I lost quite a 
bit of time looking for why it didn't ask for a passphrase. 

What version of the product are you using? On what operating system?
- cryptsetup 1.2.0
- Red Hat Enterprise Linux Server release 6.2 (Santiago)

Please provide any additional information below.
It looks like a silly bug report, but I went into it while learning my RHEL 
RHCSA certification, I'm sure some other people I've ruined into this as well. 

Thanks!!

Original issue reported on code.google.com by d4c...@gmail.com on 14 May 2014 at 7:15

[GoogleCodeExporter]

Yes, you are not the first. But this works very effectively to "force" people 
to read and understand the message before entering "yes".
(You can always use -q quiet switch to disable this completely.)

Note the "uppercase" in warning.

WARNING!
========
This will overwrite data on /x irrevocably.

Are you sure? (Type uppercase yes):

Sorry but I think the message is doing what it should.

Original comment by gmazyl...@gmail.com on 18 May 2014 at 9:30

• Changed state: WontFix

[GoogleCodeExporter]

Ok so maybe just writing "aborting" instead of returning quietly to the
shell would be easier to understand.

I understand your point, it is just that I found it misleading. When I
typed yes in lowercase, I thought there was another issue, I was wondering
why it didn't ask for a passphrase. So I started cruising around the system
to find if I did something wrong earlier. Then I found the answer on a
mailing list after 30mn.

In my opinion, it's a good idea to make sure the user read the warning, but
if you don't tell the user that he did something wrong, he will not
understand your point.

2014-05-19 3:00 GMT+05:30 <cryptsetup@googlecode.com>:

Original comment by d4c...@gmail.com on 19 May 2014 at 4:00