From: Dave <davestechshop@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: framstag@rus.uni-stuttgart.de
Subject: Re: snapshots of encrypted directories?
Date: Tue, 19 Sep 2017 14:22:06 -0400 [thread overview]
Message-ID: <CAH=dxU6DX_P8JH_VfvF1vGrH-Exm9dGceWCrGZ_AwV3fNdOWqA@mail.gmail.com> (raw)
In-Reply-To: <20170915100103.GB32347@rus.uni-stuttgart.de>
On Fri, Sep 15, 2017 at 6:01 AM, Ulli Horlacher
<framstag@rus.uni-stuttgart.de> wrote:
>
> On Fri 2017-09-15 (06:45), Andrei Borzenkov wrote:
>
> > The actual question is - do you need to mount each individual btrfs
> > subvolume when using encfs?
>
> And even worse it goes with ecryptfs: I do not know at all how to mount a
> snapshot, so that the user has access to it.
>
> It seems snapshots are incompatible with encrypted filesystems :-(
My experience is the opposite. I use dm-crypt as well as encfs with
BTRFS and everything, including snapshots, works as I would expect it
to work.
I have been able to successfully restore snapshots that contained
encrypted data.
I think the other answers have already provided more details than I
could provide, so I just wanted to add the fact that my experience has
been positive with BTRFS snapshots and encryption.
next prev parent reply other threads:[~2017-09-19 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:57 snapshots of encrypted directories? Ulli Horlacher
2017-09-14 15:32 ` Hugo Mills
2017-09-15 3:45 ` Andrei Borzenkov
2017-09-15 10:01 ` Ulli Horlacher
2017-09-15 10:15 ` Peter Becker
2017-09-15 16:28 ` Ulli Horlacher
2017-09-15 17:16 ` Austin S. Hemmelgarn
2017-09-15 19:41 ` Ulli Horlacher
2017-09-18 11:45 ` Austin S. Hemmelgarn
2017-09-19 18:22 ` Dave [this message]
2017-09-15 12:35 ` Austin S. Hemmelgarn
2017-09-15 17:25 ` Andrei Borzenkov
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='CAH=dxU6DX_P8JH_VfvF1vGrH-Exm9dGceWCrGZ_AwV3fNdOWqA@mail.gmail.com' \
--to=davestechshop@gmail.com \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).