Control: tag -1 pending
On Sat, 05 Mar 2022 at 17:17:07 +0100, Guilhem Moulin wrote:
> For do_start() we're reading crypttab(5) sequentially as we don't have
> enough information about nesting, however for do_stop() we have that
> information in the mapping table, so no need to reverse crypttab(5)
Control: retitle -1 `/etc/init.d/cryptdisks stop` should safely traverse nested
block device stacks
Control: tag -1 - moreinfo
On Sat, 05 Mar 2022 at 16:54:07 +0100, Guenther Brunthaler wrote:
> which is exactly the same as do_start() does. And hence the entries are
> processed in the same order
Am Sat, 5 Mar 2022 13:32:24 +0100
schrieb Guilhem Moulin :
> I believe cryptdisks_start(8) and cryptdisks_stop(8) processes
> mappings in the order given on the command line, which is
> intentional. Are you talking about SysV init scripts?
Yes, you are right. The problem actually refers
to "/etc
Control: tag -1 moreinfo
On Sat, 05 Mar 2022 at 13:13:57 +0100, Guenther Brunthaler wrote:
> When creating nested dmcrypt mappings in /etc/crtypttab,
> cryptdisks_start processes them from top to bottom.
I believe cryptdisks_start(8) and cryptdisks_stop(8) processes mappings
in the order given on
Package: cryptsetup
Version: 2:2.3.7-1+deb11u1
### Issue description
When creating nested dmcrypt mappings in /etc/crtypttab,
cryptdisks_start processes them from top to bottom.
The means that a some encrypted base device will be unlocked before any
nested encrypted devices based on it.
While t
5 matches
Mail list logo
