Bug#247054: Crypto-root patch updated to initrd-tools 0.1.70
On Mon, Jun 07, 2004 at 12:20:30PM +1000, Herbert Xu wrote:
> > If yes, can one also use swsusp with the saved image on lvm device?
> Yes. In fact that's one of the main reason for having it as a module
> in the first place.
Ok, I've read up a bit more about swsusp.
It looks to me like the initrd doesn't even need to setup root, right?
The boot process will replace the entire kernel, it's modules, it's idea of
root, everything. This means we just have to get the linux kernel to the
point where it can read the saved image.
Am I right about this so far?
If so, then cryptoroot support must also work with swsusp since otherwise
you could boot the system bypassing the need to gain access to the root.
The kernel would simply remember the key. Therefore, my patch must support
setting up crypto on the image device during boot.
If you agree with me so far, then what we really want to do in the initrd is
to either find root or find the swap device. Setting up encryption for one
is enough. Swsusp is controlled by a kernel-command-line option, so we
should check for the option and only if it is set, configure root.
If so, I will update my patch and setup swsusp on my machine to test it.
Wesley W. Terpstra