public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fileserver with Raid + Crypto + BtrFS
Date: Thu, 12 Nov 2015 09:01:46 +0100	[thread overview]
Message-ID: <3398618.IUVla0c3Nh@thetick> (raw)
In-Reply-To: <20151111230844.08dc2e4d@digimed.co.uk>

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

On Wednesday 11 November 2015 23:08:44 Neil Bothwick wrote:
>On Wed, 11 Nov 2015 22:18:15 +0100, Ralf wrote:
>> And thinking about btrfs snapshot feature, using some 'btrfs history
>> tool', i would probably only be able to see a lot of crypto garbage when
>> going through my history (which can for sure be accessed by ecryptfs,
>> but not by standard btrfs tools).
>
>That's a good point, you'd need to mount each snapshot before you could
>read it.
>
>I *really* wish btrfs had its own encryption, but I suspect this would be
>far from trivia to implement.

From a presentation [0] earlier this year I understand that Chris Mason really 
wants it, too, but has something else he wanted to finish first (I don't 
remember what, though).

[0] https://www.youtube.com/watch?v=W3QRWUfBua8

-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-12  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 17:09 [gentoo-user] Fileserver with Raid + Crypto + BtrFS Ralf
2015-11-11 18:19 ` Neil Bothwick
2015-11-11 21:18   ` Ralf
2015-11-11 22:54     ` Neil Bothwick
2015-11-11 23:08     ` Neil Bothwick
2015-11-12  8:01       ` Marc Joliet [this message]
2015-11-11 22:19 ` Marc Stürmer
2015-11-11 23:14 ` Nuno Magalhães
2015-11-12  6:01   ` J. Roeleveld

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=3398618.IUVla0c3Nh@thetick \
    --to=marcec@gmx.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