From: Christian Brauner <brauner@kernel.org>
To: Tyler Hicks <code@tyhicks.com>
Cc: Yangtao Li <frank.li@vivo.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
ecryptfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark ecryptfs as orphan state
Date: Mon, 3 Apr 2023 14:44:06 +0200 [thread overview]
Message-ID: <20230403-frolic-constant-bc5d0fb13196@brauner> (raw)
In-Reply-To: <ZB4nYykRg6UwZ0cj@sequoia>
On Fri, Mar 24, 2023 at 05:42:43PM -0500, Tyler Hicks wrote:
> On 2023-03-23 01:19:10, Yangtao Li wrote:
> > +cc code@tyhicks.com, ecryptfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
>
> Hey Yangtao - I think it is a good idea to deprecate eCryptfs and
> prepare for its removal in a couple years.
>
> It never received the dedication needed to sort out the stacked
> filesystem design issues and its crypto design is aging without
> updates/improvements for some time. The majority of the user base, which
> came about when Ubuntu added home dir encryption as an option in the
> installer, has greatly decreased since Ubuntu removed it from the
> installer and dropped official support several years back. Finally,
> fscrypt should provide a more than complete alternative for the majority
> of use cases.
>
> Deprecating and removing is the right thing to do.
>
> I can devote some time to limping it by until removal but would also
> appreciate a hand if anyone has time/interest.
Hey Tyler,
Do you want to send a patch to deprecate it with your SOB?
Christian
next prev parent reply other threads:[~2023-04-03 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:21 [PATCH] MAINTAINERS: mark ecryptfs as orphan state Yangtao Li
2023-03-21 6:35 ` Greg Kroah-Hartman
2023-03-22 17:18 ` Yangtao Li
2023-03-22 17:19 ` Yangtao Li
2023-03-24 22:42 ` Tyler Hicks
2023-04-03 12:44 ` Christian Brauner [this message]
2023-04-03 13:44 ` Yangtao Li
2023-04-04 2:57 ` Tyler Hicks (Microsoft)
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=20230403-frolic-constant-bc5d0fb13196@brauner \
--to=brauner@kernel.org \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=frank.li@vivo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.