From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: snapshots of encrypted directories?
Date: Fri, 15 Sep 2017 21:41:26 +0200 [thread overview]
Message-ID: <20170915194126.GF32347@rus.uni-stuttgart.de> (raw)
In-Reply-To: <6cd1ef22-7cab-4c8c-0b73-d254aeca83ad@gmail.com>
On Fri 2017-09-15 (13:16), Austin S. Hemmelgarn wrote:
> >> And then mount enryptfs:
> >>
> >> mount.ecryptfs /<MOUNTPOINT_ENCRYPTED> /<MOUNTPOINT_DECRYPTED>
> >
> > This only possible by root.
> > For a user it is not possible to have access for his own snapshots.
> > Bad.
>
> Which is why you use EncFS (which is a FUSE module that runs in
> userspace and requires no root privileges) instead of eCryptFS (which is
> a kernel assisted filesystem that doesn't use FUSE, has more complicated
> setup constraints, and requires CAP_SYS_ADMIN or root access).
I use both, encfs and ecryptfs, for different use cases.
I use ecryptfs on my notebooks for $HOME, which has some kind of
automounter on login (via pam).
This setup is not possible with encfs, which is also much slower and has
a lower security level.
But even for encfs it is very circumstantial for a user to have access to
snapshots.
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<6cd1ef22-7cab-4c8c-0b73-d254aeca83ad@gmail.com>
next prev parent reply other threads:[~2017-09-15 19:41 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 [this message]
2017-09-18 11:45 ` Austin S. Hemmelgarn
2017-09-19 18:22 ` Dave
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=20170915194126.GF32347@rus.uni-stuttgart.de \
--to=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).