From: Tyler Hicks <tyhicks@canonical.com>
To: Thiago Padilha <tpadilha84@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Storing the executable bit along with the rest of cryptographic metadata
Date: Thu, 31 Jan 2013 09:29:08 -0800 [thread overview]
Message-ID: <20130131172907.GA3422@boyd> (raw)
In-Reply-To: <CAAq2XdoN6E0xGyn-cVBTvVjmXZ7i2bpfDrdhC9FjB60_DPerWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On 2013-01-31 09:58:01, Thiago Padilha wrote:
> I'm trying to use a directory in a NTFS external drive as the lower
> mount for ecryptfs, but since ntfs doesn't understand the concept of
> executable files, every file is treated as executable by ntfs-3g
>
> Is there a mount option to override the lower encrypted file
> permissions by permissions stored elsewhere(perhaps in the encrypted
> file header) ?
No, sorry. That's not something that eCryptfs will ever do.
Tyler
> --
> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-31 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 12:58 Storing the executable bit along with the rest of cryptographic metadata Thiago Padilha
2013-01-31 17:29 ` Tyler Hicks [this message]
[not found] ` <CAPv9ZmndfGvgdEhHaie9Sm81pZ+mPfTRX67EGRPN8B4r96RKHQ@mail.gmail.com>
2013-02-01 12:40 ` Thiago Padilha
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=20130131172907.GA3422@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=tpadilha84@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.