Control: tags 1000648 pending
Paul Slootman wrote...
> Perhaps this info could be added to a README.Debian in the clevis-luks
> package? I looked for any documentation but unfortunately there isn't
> any... I'd consider this bug closed if the initramfs option for crypttab
> was mentioned in a
On Fri 26 Nov 2021, Paul Slootman wrote:
>
> The reason I think is that the second device is not needed to boot the
> system. Presumably there is some way that the initrd scripts determine
> what devices need to be decrypted; my problem would probably go away if
> the second device gets added to
On Fri 26 Nov 2021, Christoph Biedl wrote:
> Paul Slootman wrote...
>
> > I have 2 MD raid devices which are encrypted.
> (...)
> > I can't find any hints on how to proceed from here, to have the second
> > device also automatically unlocked. Do you have any idea?
> > I can't be the only person
Paul Slootman wrote...
> I have 2 MD raid devices which are encrypted.
(...)
> I can't find any hints on how to proceed from here, to have the second
> device also automatically unlocked. Do you have any idea?
> I can't be the only person with more than one LUKS-encrypted device.
Strange - at a
Source: clevis
Version: 16-2
Severity: normal
I have 2 MD raid devices which are encrypted.
/dev/md1 is a PV for LVM which contains basically the root filesystem
and separate /var and /tmp filesystems.
/dev/md2 is also a PV for LVM contains /home and other filesystems.
I have bound both to the
5 matches
Mail list logo
