Poky Project Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "poky@pokylinux.org" <poky@pokylinux.org>
Cc: scott.m.rifenbark@intel.com
Subject: Warning - don't use eCryptFS
Date: Tue, 30 Nov 2010 15:05:41 +0000	[thread overview]
Message-ID: <201011301505.42532.paul.eggleton@linux.intel.com> (raw)

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:

  * pseudo-native failing to write an sstate package ("file name too long" - apparently eCryptFS is limited to ~140 characters due to design limitations)

  * ncurses-native failing at do_install (some kind of interference with libtool that caused it to write an invalid path to the libncurses.la file, I didn't track down the exact cause as it went away when I stopped using eCryptFS. Might be indirectly related to the name length limitation.)

Scott, could you please add a warning to the documentation not to use eCryptFS with poky? In particular, it should not be used to store TMPDIR and SSTATE_DIR.

I'll follow up soon with a patch that will do a sanity check on the file name length limit - this will catch any other weird file systems that might cause these kinds of issues.

Cheers,
Paul  


             reply	other threads:[~2010-11-30 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 15:05 Paul Eggleton [this message]
2010-11-30 16:05 ` Warning - don't use eCryptFS Bruce Ashfield
2010-12-08 18:06 ` Darren Hart

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=201011301505.42532.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=poky@pokylinux.org \
    --cc=scott.m.rifenbark@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox