public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dm-crypt + ext4 = where will the journal go?
Date: Tue, 04 Sep 2012 22:45:07 +0200	[thread overview]
Message-ID: <50466853.5070704@binarywings.net> (raw)
In-Reply-To: <20120904211426.3acc7267@hactar.digimed.co.uk>

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

Am 04.09.2012 22:14, schrieb Neil Bothwick:
> On Tue, 04 Sep 2012 20:59:34 +0200, Florian Philipp wrote:
> 
>> I just have to make sure to leave nothing private on root, /usr or /etc.
> 
> Like your passwd and shadow files?
> 
> 

*g*, good point. However, I'm willing to take the risk on just these
two: passwd doesn't contain anything of considerable interest. shadow
contains exactly two passwords, both as sha256-sums (or similar, did not
really check). The passwords themselves are in excess of 90 bit entropy,
depending on how you estimate it.

Most of the rest which might be of interest and is usually in /etc can
be symlinked there from a safe location in /var.

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-09-04 20:51 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 [this message]
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   ` Aw: " "Roland Häder"
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=50466853.5070704@binarywings.net \
    --to=lists@binarywings.net \
    --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