tag 614118 +wontfix thanks Hello Harald,
On 19/02/2011 Harald Dunkel wrote: > cryptsetup shouldn't be so picky about upper and lower case characters > on the command line. The current options "LuksOpen", "LuksClose", etc. > have no advantage over "luksopen", "luksclose", etc. but they are much > more error-prone. case-insensitive commandline argements are rather uncommon. the cryptsetup upstream maintainer already stated that he's not willed to change this common practise for cryptsetup. i'll tag this bugreport as wontfix, even though I'd prefer to simply close it. maybe you could comment on the conversation with milan and close the bugreport yourself if you're ok with the explanation. see my conversation with milan broz: regarding this bug: > On 02/20/2011 06:45 PM, Jonas Meurer wrote: > > To me it's a matter of taste whether the cryptsetup commands are > > case-sensitive or not. One might either argue that it doesn't hurt to > > support lowercase commands like 'luksformat' and 'luksopen' as well, or > > argue that commandline options are _always_ case-sensitive for common > > commandline applications. > > and passphrases are also case sensitive:-) > > > > > If you decide that cryptsetup commands stay case sensitive, then I'll > > simply tag the bugreport as wontfix. > > Well, I did not invented that, I do not like combined case commands there > too much but I do not want to change it now (most users which have problems > here will use some GUI wrapper or so anyway). > > Argument is the same like for "type uppercase yes" - it forces people > to think before it blindly answer yes or issue some command. > You should have some uppercase chars in passphrase so using it in command > should not hurt:-) greetings, jonas
signature.asc
Description: Digital signature
