EcryptFS development
 help / color / mirror / Atom feed
From: David Obadia <dav-ecryptfs@odav.org>
To: ecryptfs@vger.kernel.org
Subject: Re: Wrapper to mount Private directories without root
Date: Tue, 15 Jan 2013 23:59:44 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130116T004804-557@post.gmane.org> (raw)
In-Reply-To: 20130115191820.GA5302@boyd

Tyler Hicks <tyhicks <at> canonical.com> writes:
> On 2012-12-12 16:58:41, David Obadia wrote:
> > Not sure why ecryptfs-recover-private requires root, I've found a way to do 
the
> > same thing without root.
> 
> A quick glance at that script shows that it needs root to do the
> `mount -t ecryptfs ...` command. The main eCryptfs mount helper
> (/sbin/mount.ecryptfs) is big and complex.

Understood, that makes sense. That script might pre-date mount.ecryptfs_private? 
I say this because I was able to achieve the same functionality using only 
mount.ecryptfs_private, not mount.ecryptfs in my Python script.

> > Also I think it would be helpful to have a user friendly API for
> > creating/mounting/unmounting ecrypted folders that doesn't require root 
using
> > the setuid in mount.ecryptfs_private.
> 
> That might be a nice thing to have, but we want mount.ecryptfs_private
> to stay as simple as possible so that it can be audited and so that we
> don't introduce new security flaws into the code. It is intentionally
> locked down to do very specific actions.

Sounds reasonable. Maybe providing a wrapper script gives the best of both 
world? 
1) Minimizes the amount of setuid code that needs to be audited
2) Gives flexibility to the end-user to do as much as can possibly be done, in a 
user-friendly manner, and without requiring root access.

Would be glad to help,
David- 

      reply	other threads:[~2013-01-15 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 16:58 Wrapper to mount Private directories without root David Obadia
2013-01-15 19:18 ` Tyler Hicks
2013-01-15 23:59   ` David Obadia [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=loom.20130116T004804-557@post.gmane.org \
    --to=dav-ecryptfs@odav.org \
    --cc=ecryptfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox