Closed GoogleCodeExporter closed 9 years ago
The /etc/cryptab and /etc/fstab is outside of cryptsetup package scope.
It is init system responsibility to parse this (e.g. initscripts or systemd).
Yes, device-maper subsystem need internal changes to allow activation of device
from non-superuser account.
I cannot do anything here until some patch is added to kernel allowing this.
For the cryptmout:
The problem WAS that they did not use libcryptsetup but simply copied half of
the libcryptestup source directly. But I see that version 5 uses libcryptsetup,
that's great news!
So in principle this could work but I would definitely prefer device-mapper in
kernel allows "private" user-only manageable devices...
Anyway, closing this, the crypttab handling is done elsewhere. (Maybe
systemd-cryptsetup could add this but I am really not sure if it is good idea
without direct kernel support.)
Original comment by gmazyl...@gmail.com
on 5 Nov 2014 at 8:38
Original issue reported on code.google.com by
jon...@gmail.com
on 3 Nov 2014 at 10:23