Jari Ruusu wrote: > Matthias Schniedermeyer wrote: >>> 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. > > Ok, ok. > > It wasn't a big change. 22 code lines changed, not counting documentation > changes. It was a matter of adding a mount option and open/close a file, > otherwise it uses existing code paths. Now mount has a new mount option > 'cleartextkey' which specifies a file that holds 65 lines of key data, i.e. > unencrypted contents of gpg encrypted key file. Some examples follows. Great. Thanks. Bis denn -- 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/
