From: Tyler Hicks <tyhicks@canonical.com>
To: Lance Reed <reed.r.lance@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
Date: Wed, 26 Feb 2014 12:00:45 -0600 [thread overview]
Message-ID: <20140226180044.GA5056@boyd> (raw)
In-Reply-To: <loom.20140226T165932-775@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2791 bytes --]
Hi Lance!
On 2014-02-26 16:06:20, Lance Reed wrote:
> I am attempting to setup encrypted user home directories via eCryptfs using
> gluster as a backend.
>
> Very simple setup currently has a small two node gluster cluster mounted by
> a separate client. Normal gluster client and NFS mount / file options are
> working fine.
>
>
> e.g. https://wiki.archlinux.org/index.php/ECryptfs#Encrypting_a_home_directory
>
> In my attempts lay ecryptfs on top of the mounted native gluster setup, I am
> unable to edit a file, write etc. I either get zero length or fixed sizes.
>
> Only log messages I get are:
> "Either the lower file is not in a valid eCryptfs format, or the key could
> not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO"
>
> I am posting in this forum to see if anyone knows of any reason why this may
> be failing from the ecryptfs side and I should stop banging my head against
> the wall...
>
> I am trying Centos / RHEL.
> See these bugs:
> Bug 762976 - (GLUSTER-1244) ecryptfs does not work when the directory to be
> encrypted is on gluster mount
> https://bugzilla.redhat.com/show_bug.cgi?id=762976
>
> A non-empty file created on glusterfs with ecryptfs reports as a file of
> size zero
> https://bugzilla.redhat.com/show_bug.cgi?id=989702#c1
>
> These look to be issues with O_DIRECT usage in fuse but are suppose to be
> fixed now.
>
> I was hoping someone might have an idea or remember some of this to help me
> figure out if using glusterfs for a backend with eCryptfs is even an option.
eCryptfs mounted on top of glusterfs is something that I've never tried
and I don't recall anyone talking with upstream eCryptfs about it,
either. It wouldn't surprise me if it doesn't work. :/
I haven't paid much attention to glusterfs, but I thought the answer to
encryption with glusterfs was hekafs?
While briefly refreshing my memory on hekafs, it sounds like it is
geared towards cloud storage providers. Maybe it is too complex for your
needs?
>
> Is it possible that this bug is still the core problem?
> "ecryptfs does not work properly over nfs, cifs, samba, WebDAV, or aufs"
> https://bugs.launchpad.net/ecryptfs/+bug/277578
> It is old but still seems to be open..
That bug is a mess. It needs to be reevaluated and split up into
separate bug reports for individual lower filesystems. There is no
single fix for that bug and it will never be closed in its current
state.
>
> versions of the code I am using:
> glusterfs-cli-3.4.2-1.el6.x86_64
> glusterfs-libs-3.4.2-1.el6.x86_64
> glusterfs-fuse-3.4.2-1.el6.x86_64
> glusterfs-server-3.4.2-1.el6.x86_64
> ecryptfs-utils-82-6.el6_1.3.x86_64
> glusterfs-3.4.2-1.el6.x86_64
Kernel version?
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-02-26 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:06 Can anyone confirm or deny if ecryptfs will work with a glusterfs backend? Lance Reed
2014-02-26 18:00 ` Tyler Hicks [this message]
2014-02-26 18:35 ` Lance Reed
2014-02-26 19:56 ` Tyler Hicks
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=20140226180044.GA5056@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=reed.r.lance@gmail.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.