All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: Warning - don't use eCryptFS
Date: Wed, 08 Dec 2010 10:06:33 -0800	[thread overview]
Message-ID: <4CFFC929.50501@linux.intel.com> (raw)
In-Reply-To: <201011301505.42532.paul.eggleton@linux.intel.com>

On 11/30/2010 07:05 AM, Paul Eggleton wrote:
> Hi all,
>
> FYI I recently had some fairly serious problems with poky and the
> "encrypted home directory" function in Ubuntu, which uses eCryptFS.
> Problems I experienced included:

I've also experienced git tree corruption when using eCryptFS for my
home directory. It's definitely on my "avoid like the plague" list. I
had no such issues while using the /etc/crypttab mechanism (I forget
what the right name is for that). But Ubuntu broke that with Upstart (at
least for me).

-- 
Darren Hart
Yocto Linux Kernel


      parent reply	other threads:[~2010-12-08 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 15:05 Warning - don't use eCryptFS Paul Eggleton
2010-11-30 16:05 ` Bruce Ashfield
2010-12-08 18:06 ` Darren Hart [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=4CFFC929.50501@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@pokylinux.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 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.