All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Frederick Gazerblezeebe <fgazerblezeebe@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: loop-aes encrypted root on Fedora 15 using systemd
Date: Fri, 03 Jun 2011 20:38:21 +0300	[thread overview]
Message-ID: <4DE91C0D.3D9BB471@users.sourceforge.net> (raw)
In-Reply-To: BANLkTimeDeisn6h9VRn9CLfZyLe=biVTEw@mail.gmail.com

Frederick Gazerblezeebe wrote:
> /dev/loop2: [0001]:5099 (/dev/sda2) encryption=AES128 multi-key-v3
> /dev/loop3: [0702]:2104244 (/dev/sda3) encryption=AES128 multi-key-v3
> 
> but systemd is unable to mount it to /home as defined in fstab,
> 
> /dev/loop3      /home      ext4    defaults        0 2    #/dev/sda3

Does it work if you remove #/dev/sda3 text at the end of the line? Strict
reading of fstab(5) man page says that lines that begin with # are comments.
Mount program fstab parser code seems to be happy with extra stuff at end of
line, but other fstab parser implementations are not necessarily ok with
that.

> One additional peculiarity is that although the swap is activated at
> boot time, it is not  encrypted until I remove/add it again.  The
> fstab entry is
> 
> /dev/sda5       swap       swap    sw,loop=/dev/loop5,encryption=AES128   0 0

That sounds like systemd is not using swapon program to enable swap. Does it
work if you set it up with non-changing encryption keys? As in,
build-initrd.sh sets it up, and /etc/fstab line is:

/dev/loop5  swap  swap  sw  0  0

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

  reply	other threads:[~2011-06-03 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 21:31 loop-aes encrypted root on Fedora 15 using systemd Frederick Gazerblezeebe
2011-05-31 12:59 ` Jari Ruusu
2011-06-02  3:10   ` Frederick Gazerblezeebe
2011-06-03 16:42   ` Frederick Gazerblezeebe
2011-06-03 17:38     ` Jari Ruusu [this message]
2011-06-03 21:34       ` Frederick Gazerblezeebe
2011-06-04  7:27         ` Jari Ruusu
2011-06-07 14:28           ` Frederick Gazerblezeebe
2011-06-29 16:42 ` Frederick Gazerblezeebe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DE91C0D.3D9BB471@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=fgazerblezeebe@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.