From: Li Wang <liwang@ubuntukylin.com>
To: Karl-Philipp Richter <krichter722@aol.de>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Filesystem boundaries
Date: Mon, 08 Jul 2013 09:05:22 +0800 [thread overview]
Message-ID: <51DA1052.2060606@ubuntukylin.com> (raw)
In-Reply-To: <51D6E23A.7000103@aol.de>
Are those subdirs basically symbol links to somewhere else not inside
the eCryptfs dir? Then those dirs won't be encrypted by eCryptfs.
For native subdirs, eCryptfs could not exclude them for being encrypted.
On 07/05/2013 11:11 PM, Karl-Philipp Richter wrote:
> Hi together,
> I'm new to mailing list and hope to be at the right address. I tried to
> figure out how to prevent ecryptfs to cross file system borders or
> exclude subdirectories of the source directory (the current setup is
> that I linked a lot of directories from an encrypted disk, which don't
> need encryption). I guess it's explained somewhere. So I'd rather
> suggest to put it on the man page.
>
> Greetings, Kalle
>
next prev parent reply other threads:[~2013-07-08 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 15:11 Filesystem boundaries Karl-Philipp Richter
2013-07-08 1:05 ` Li Wang [this message]
2013-07-08 5:26 ` Karl-Philipp Richter
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=51DA1052.2060606@ubuntukylin.com \
--to=liwang@ubuntukylin.com \
--cc=ecryptfs@vger.kernel.org \
--cc=krichter722@aol.de \
/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).