[pkg-cryptsetup-devel] Bug#471727: Bug#471727: passdev keyscript

[Jonas Meurer]

On 29/07/2008 Christoph Anton Mitterer wrote:
> On Tue, 2008-07-29 at 12:00 +0200, Jonas Meurer wrote:
> > I'm not sure that I understand what you mean. If you want your keyscript
> > to mount any removable media to read the keyfile from, passdev is the
> > way to go. If you don't need that, simply don't use passdev.
> > In case that you want to support both, just check for existance of the
> > keyfile *in your keyscript* and invoke passdev only when the keyfile is
> > not available yet.
>
> 1) I consider the work of passdev as general functionality,.. that
> probably every keyscript could use,... thus each keyscript would have to
> contain that check, right?
> Why introduce such a redundancy if passdev could be used always and
> automatically (transparent for the keyscript).

You may be right that several keyscripts could benefit from using
passdev to make a keyfile available, but keyscripts are not restricted
to keyfile processing after all.

Imagine a perfectly valid (from the keyscript interface point of view)
keyscript which does nothing else than 'echo thisismykeys'.

I still object against more complex keyscript preprocessing in the
cryptdisks initscript.

Anyway, this discussion is completely off-topic for the bugreport in
question. Please reply to pkg-cryptsetup-devel at lists.alioth.debian.org
only in case that you want it to continue.

greetings,
 jonas