public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alonbl@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems with loop-aes
Date: Wed, 7 May 2014 09:48:19 +0300	[thread overview]
Message-ID: <CAOazyz3_zLfv3AMD9uESprxyC2BCdu30eqH7P_cqTgcNY88LPg@mail.gmail.com> (raw)
In-Reply-To: <20140507043647.GA32390@waltdnes.org>

On Wed, May 7, 2014 at 7:36 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>
> On Wed, May 07, 2014 at 12:50:53AM +0300, Alon Bar-Lev wrote
> > Checkout[1]
> >
> > [1]
> > http://alonbl.shoutwiki.com/wiki/Gentoo/Linux_Disk_Encryption_Using_LoopAES_And_SmartCards
>
>   Unfortunately, 90% of the wiki entry is irrelavant to my situation.
> It's aimed at encrypting the entire machine, and making it bootable with
> initramfs.  I just need to encrypt a USB key.

Encrypting USB key without booting from it?

>   I see that it also says to build various stuff with the "static" USE
> flag.  I assume this is for an initramfs boot.  Looking at the ebuild, I
> see that it strongly suggests static-libs builds for a whole bunch of
> stuff.  I don't know if this is required in all cases, or simply for
> booting from an encrypted disk...
>
> LIB_DEPEND="dev-libs/libgpg-error[static-libs(+)]
>         dev-libs/popt[static-libs(+)]
>         sys-apps/util-linux[static-libs(+)]
>         gcrypt? ( dev-libs/libgcrypt:0[static-libs(+)] )
>         nettle? ( >=dev-libs/nettle-2.4[static-libs(+)] )
>         openssl? ( dev-libs/openssl[static-libs(+)] )
>         sys-fs/lvm2[static-libs(+)]
>         sys-libs/e2fsprogs-libs[static-libs(+)]
>         udev? ( virtual/udev[static-libs(+)] )"
>
>   Also interesting is that this webpage recommends *NO* loop support in
> the kernel.  This may be important, i.e. loop-aes may provide the
> support, and clash with the kernel code.  Time to head off to bed
> tonight.  I'll try again in the morning.

Correct. If you want to use loop-aes you must disable the kernel loop,
this is how things are done.

Alon


      reply	other threads:[~2014-05-07  6:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 18:31 [gentoo-user] Problems with loop-aes Walter Dnes
2014-05-06 18:45 ` J. Roeleveld
2014-05-06 21:34   ` Walter Dnes
2014-05-07  6:11     ` J. Roeleveld
2014-05-07 18:11       ` [gentoo-user] [SOLVED] Running cryptsetup under mdev Walter Dnes
2014-05-07 18:57         ` J. Roeleveld
2014-05-08 10:36           ` Andrew Savchenko
2014-05-12  6:51             ` J. Roeleveld
2014-05-12  7:21           ` Matti Nykyri
2014-05-12  7:24           ` Matti Nykyri
2014-05-06 21:50 ` [gentoo-user] Problems with loop-aes Alon Bar-Lev
2014-05-07  4:36   ` Walter Dnes
2014-05-07  6:48     ` Alon Bar-Lev [this message]

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=CAOazyz3_zLfv3AMD9uESprxyC2BCdu30eqH7P_cqTgcNY88LPg@mail.gmail.com \
    --to=alonbl@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox