On Sat, 07 Jul 2018 at 01:52:46 +0200, Christoph Anton Mitterer wrote:
> So the use case is, that people may also wish to modify parts of the 
> ../cryptroot/crypttab file from their hook scripts... and that it
> could be nice to have an interface for that as well.

That adds too much complexity for the benefit of a too specific use
case, IMHO.  Since you already “abuse” CRYPTTAB_KEY and parse/split its
value in your hook and keyscript, you could as well but both the source
and destination path there:

    device=…:pathsrc=…:pathdst=…

Or have a static destination path that uniquely depends on $CRYPTTAB_NAME,
for instance [$DESTINATION]/cryptroot/keyfiles/$CRYPTTAB.key.

-- 
Guilhem.

Attachment: signature.asc
Description: PGP signature

Reply via email to