Re: Mounting additional encrypted filesystems from within an encrypted root

--0016e64b9602e0fba904758ebf86
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 9, 2009 at 8:21 PM, markus reichelt <[email protected]> wrote:

>
> maybe copy gpg to /bin ? (it's mentioned in loop-AES.README, section
> 5)
>
> Thanks for suggesting I go back and check that!  For reasons that escape me
right now, I had placed gpg in /sbin instead of /bin.  Moving it to /bin
enabled losetup.sh to run successfully, at least from the commandline.

The final stumbling block was that because /etc/rc.d/rc#.d/S00losetup (a
link to losetup.sh) was called too late in the boot sequence, the boot still
failed when it tried to fsck loop6 before it had been losetup'ed.  I solved
this by adding the losetup line to /etc/rc.d/rc.sysinit immediately before
the fsck calls.

Of course this isn't ideal as I'll need to re-edit rc.sysinit everytime the
init scripts are updated, but that's actually less of a concern to me than
having plaintext passphrases on my system.  So now that things are at least
working, I think I'll revisit my original plan of having all the partitions
losetup/mounted within the initial initrd, ideally after entry of a single
passphrase.

FG

--0016e64b9602e0fba904758ebf86
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 9, 2009 at 8:21 PM, markus reichelt <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]">[email protected]</a>&gt;</span> wrote:<br><d=
iv class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"border-=
left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left=
: 1ex;">
<div class=3D"im"><br>
maybe copy gpg to /bin ? (it&#39;s mentioned in loop-AES.README, section<br=
>
</div><div><div></div><div class=3D"h5">5)<br>
<br></div></div></blockquote><div>Thanks for suggesting I go back and check=
 that!=A0 For reasons that escape me right now, I had placed gpg in /sbin i=
nstead of /bin.=A0 Moving it to /bin enabled losetup.sh to run successfully=
, at least from the commandline.<br>
<br>The final stumbling block was that because /etc/rc.d/rc#.d/S00losetup (=
a link to losetup.sh) was called too late in the boot sequence, the boot st=
ill failed when it tried to fsck loop6 before it had been losetup&#39;ed.=
=A0 I solved this by adding the losetup line to /etc/rc.d/rc.sysinit immedi=
ately before the fsck calls.<br>
<br>Of course this isn&#39;t ideal as I&#39;ll need to re-edit rc.sysinit e=
verytime the init scripts are updated, but that&#39;s actually less of a co=
ncern to me than having plaintext passphrases on my system.=A0 So now that =
things are at least working, I think I&#39;ll revisit my original plan of h=
aving all the partitions losetup/mounted within the initial initrd, ideally=
 after entry of a single passphrase.<br>
<br>FG<br><br></div></div>

--0016e64b9602e0fba904758ebf86--

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/