Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i78e14604:Fastmail
Date:   Fri, 24 Mar 2023 17:42:43 -0500
From:   Tyler Hicks <code@tyhicks.com>
To:     Yangtao Li <frank.li@vivo.com>
Cc:     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
Message-ID: <ZB4nYykRg6UwZ0cj@sequoia>
References: <ZBlQT2Os/hB2Rxqh@kroah.com>
 <20230322171910.60755-1-frank.li@vivo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230322171910.60755-1-frank.li@vivo.com>
Precedence: bulk

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.

Tyler

> 
> Thx,
> Yangtao