All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl-Philipp Richter <krichter722@aol.de>
To: Li Wang <liwang@ubuntukylin.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Filesystem boundaries
Date: Mon, 08 Jul 2013 07:26:16 +0200	[thread overview]
Message-ID: <51DA4D78.7040200@aol.de> (raw)
In-Reply-To: <51DA1052.2060606@ubuntukylin.com>

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

Hi Li,
thanks for your answer. In this case I obviously have a problem: My /
drive has 30 GB capacity (Ubuntu takes 10 GB (outside the encypted ~)
max. My data is linked to ~ from /mnt/xy and ~ contains effectively less
than 500 MB, but ~/home/.ecryptfs has about 20 GB. Can you point me into
a direction how to debug this (I know that I'm on dev list where this
doesn't belong... I opened
http://askubuntu.com/questions/317391/how-to-prevent-ecryptfs-from-crossing-filesystem-boundaries)?

Greetings, Kalle

Am 08.07.2013 03:05, schrieb Li Wang:
> 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
>>



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

      reply	other threads:[~2013-07-08  5:33 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
2013-07-08  5:26   ` Karl-Philipp Richter [this message]

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=51DA4D78.7040200@aol.de \
    --to=krichter722@aol.de \
    --cc=ecryptfs@vger.kernel.org \
    --cc=liwang@ubuntukylin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.