From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: John Stultz <jstultz@google.com>, Arnd Bergmann <arnd@arndb.de>,
Matthew Wilcox <willy@infradead.org>,
Arnd Bergmann <arnd@kernel.org>, Tyler Hicks <code@tyhicks.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ecryptfs is unmaintained and untested
Date: Tue, 14 Oct 2025 21:31:13 -0400 [thread overview]
Message-ID: <20251015013113.GB721110@mit.edu> (raw)
In-Reply-To: <20251014203535.GA1916@quark>
On Tue, Oct 14, 2025 at 01:35:35PM -0700, Eric Biggers wrote:
> I've been maintaining the 'fscrypt' userspace tool, and in the past I've
> done quite a bit of work to improve it. I also use it to encrypt the
> home directory on my personal desktop.
Do you have integration with PAM? I assume you must if you are
encrypting your home directory, since there would need to have some
way to insert the key to unlock your home directory as part of
single-sign on. Or are you only encrypting something like the Private
directory on your home directory, and entering the password separately
fromo the login password.
One of the really nice things of the ecryptfs integration, especialy
on Ubuntu (and I don't remember if Tyler was responsible for that
work; if so, kudos!) wasthat it was particularly eeamless.
- Ted
next prev parent reply other threads:[~2025-10-15 1:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 14:18 [PATCH] eccryptfs: select CONFIG_BUFFER_HEAD Arnd Bergmann
2024-10-28 15:02 ` ecryptfs is unmaintained and untested Matthew Wilcox
2024-10-28 21:50 ` Arnd Bergmann
2024-10-29 4:33 ` Theodore Ts'o
2024-10-30 21:06 ` Tyler Hicks
2026-02-16 11:53 ` René Herman
2025-10-14 6:07 ` John Stultz
2025-10-14 14:39 ` Theodore Ts'o
2025-10-14 16:38 ` John Stultz
2025-10-14 16:54 ` Martin Steigerwald
2025-10-14 17:52 ` Theodore Ts'o
2025-10-14 16:52 ` Martin Steigerwald
2025-10-14 20:35 ` Eric Biggers
2025-10-15 1:31 ` Theodore Ts'o [this message]
2025-10-15 2:23 ` Eric Biggers
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=20251015013113.GB721110@mit.edu \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=code@tyhicks.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ebiggers@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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