Re: Loop-AES: Question for Password when none is needed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jari Ruusu wrote:
> Matthias Schniedermeyer wrote:
>> Or another alternative: a option "keycommand=<..>" to execute print the
>> key to its stdout.
>>
>> But the tricky think here would be how to pass the necessary information
>> to the keycommand so that it can decide on which key to pass on.
> 
> Both losetup and mount can read full 65 line unencrypted key data using -p
> command line parameter. That feature can not be enabled using mount option,
> and when you think about it, it makes more sense that way.

Ask 10 people and you get at least 11 options about makes sense and what not, regardless of topic.

Having script calling mount doesn't make more sense than mount calling script

X -> Y vs. Y -> X

As i said, the only 'tricky' part in the later case is passing over the parameters so the script can decide what to do.
In the script calls mount-case the parameter passing is mostly solved in some other way, but still the script has to have some way to 'know' what it must do.

To make things short. I don't share the opinion that is makes 'more sense'.

> This problem can be summarized as: You don't want to configure your
> automounter to pass -p command line parameter to mount. The fix is:
> Reconfigure your automounter. Problem solved.

No. In the used configuration the automounter just only supports passing "-o"-options.
AND in a configuration where the automounter would support it, i would lose the 'ghosting' feature where all possible mount-point are shown, regardless if they currently are mounted or not.
I'm a commandline-person and i would loose TAB-completition, which i dislike like hell.
So it's choosing the lesser evil, which currently having to live with stupid lines in Syslog.

And i don't see why that should be changed to WORKAROUND a dumb: 'always ask for password, regardless if it is needed or not'.




-- 
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.


-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux