All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: David Obadia <dav-ecryptfs@odav.org>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Wrapper to mount Private directories without root
Date: Tue, 15 Jan 2013 11:18:20 -0800	[thread overview]
Message-ID: <20130115191820.GA5302@boyd> (raw)
In-Reply-To: <loom.20121212T175359-906@post.gmane.org>

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

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. It hasn't been security
audited and setting the setuid bit on it (which would give non-root
users sufficient privilege to perform generic eCryptfs mounts) is a bad
idea because there are likely security bugs in that program.

> 
> 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.

Tyler

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-15 19:18 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 [this message]
2013-01-15 23:59   ` David Obadia

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=20130115191820.GA5302@boyd \
    --to=tyhicks@canonical.com \
    --cc=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 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.