public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Roland Häder\"" <r.haeder@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Aw: Re: [gentoo-user] dm-crypt + ext4 = where will the journal go?
Date: Mon, 3 Sep 2012 22:52:54 +0200 (CEST)	[thread overview]
Message-ID: <trinity-1427fe2b-18a7-4306-82e8-b93e0601cea7-1346705574397@3capp-webde-bs27> (raw)
In-Reply-To: <504515AC.9060603@binarywings.net>

> You forgot the link to [1].
Already mailed but here again:
http://wiki.gentoo.org/wiki/DM-Crypt

> Never used loop-aes myself. Sorry if I miss the reason for your
> confusion because of it.
http://loop-aes.sourceforge.net

There is the source code. It needs patched util-linux(-ng) package to get working. Also you should not use (crypt-)loop because it conflicts with it (see README inside tar ball). It also provides a really simple swap encryption:

- /etc/fstab -
/dev/blaX       none    swap    sw,loop=/dev/loop0,encryption=AES256,itercountk=100     0       0

This will make sure that everytime you bootup your system a new encryption is setup with an iteration of 100 (still performant enough for most things).

> Opening a dmcrypt volume creates a mapped block device in /dev/mapper.
> You treat it like a partition and format it with ext4. Unless you use
> some exotic flags for mke2fs, the journal will be put on the same block
> device and is encrypted along with the rest of it.
> 
> So: No need to worry about it.
Thank you for the explanation. Maybe it should be added to the wiki?

> 
> Hope this helps,
> Florian Philipp
Sure it does. :)

Roland


  reply	other threads:[~2012-09-03 20:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 20:20 [gentoo-user] dm-crypt + ext4 = where will the journal go? "Roland Häder"
2012-09-03 20:36 ` Aw: " "Roland Häder"
2012-09-03 20:52   ` Florian Philipp
2012-09-03 21:23     ` Aw: " "Roland Häder"
2012-09-03 22:12       ` "Roland Häder"
2012-09-04 13:48         ` "Roland Häder"
2012-09-04 14:15           ` Dale
2012-09-04 15:14             ` Alan McKinnon
2012-09-04 15:53               ` Dale
2012-09-04 16:10                 ` Michael Mol
2012-09-04 20:09                 ` Neil Bothwick
2012-09-04 20:51                   ` Florian Philipp
2012-09-04 15:59             ` Aw: Re: " "Roland Häder"
2012-09-04 17:37           ` Aw: " Hinnerk van Bruinehsen
2012-09-04 18:18             ` Florian Philipp
2012-09-04 18:27               ` Michael Mol
2012-09-04 19:09                 ` Florian Philipp
2012-09-04 20:05                   ` Aw: " "Roland Häder"
2012-09-04 20:15                     ` Hinnerk van Bruinehsen
2012-09-04 18:48             ` Michael Hampicke
2012-09-04 20:08               ` Hinnerk van Bruinehsen
2012-09-04 20:15             ` Neil Bothwick
2012-09-04 18:33         ` Florian Philipp
2012-09-04 19:40           ` Aw: " "Roland Häder"
2012-09-04 19:47             ` Michael Mol
2012-09-04 20:36             ` Florian Philipp
2012-09-04 18:59       ` Florian Philipp
2012-09-04 20:14         ` Neil Bothwick
2012-09-04 20:45           ` Florian Philipp
2012-09-04 21:10             ` Neil Bothwick
2012-09-04 22:03               ` Samurai
2012-09-05 16:04                 ` Aw: " "Roland Häder"
2012-09-05 16:12                   ` Michael Mol
2012-09-05 18:18                     ` Aw: " "Roland Häder"
2012-09-05 22:10                       ` Florian Philipp
2012-09-06 14:20                         ` Aw: " "Roland Häder"
2012-09-06 15:36                           ` "Roland Häder"
2012-09-03 20:40 ` Florian Philipp
2012-09-03 20:52   ` "Roland Häder" [this message]
2012-09-03 20:51 ` Steve Buzonas

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=trinity-1427fe2b-18a7-4306-82e8-b93e0601cea7-1346705574397@3capp-webde-bs27 \
    --to=r.haeder@web.de \
    --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