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

Christoph Anton Mitterer christoph.anton.mitterer at physik.uni-muenchen.de
Tue Jul 29 11:19:13 UTC 2008


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).

2) Every keyscript that would like to use passdev, would have to add
some word splitting code, that processes the source:file syntax that a
users sets in /etc/crypttab

> I don't see any reason to do that.
...

> Please stop requesting the
> implementation of any random function in cryptdisks only because you
> think that it would be useful for your keyscript.
I don't that this would only be useful for my keyscript. Other
keyscripts like decrypt_ssl have probably the same problem?


Chris.






More information about the pkg-cryptsetup-devel mailing list