Bug#928956: Document removal of ecryptfs-utils from Buster
On Mon, Jul 01, 2019 at 11:52:42PM +0900, Osamu Aoki wrote:
> Hi,
>
> On Sat, Jun 29, 2019 at 10:05:39AM +0200, Paul Gevers wrote:
> > Hi all,
> >
> > On 01-06-2019 22:06, Paul Gevers wrote:
> > > On Wed, 15 May 2019 13:00:52 +0100 Justin B Rye
> > > <justin.byam.rye@gmail.com> wrote:
> > >> Daniel Lange wrote:
> > >>>> * reason for removal
> > >>>> not essential, but it helps to understand the issue
> > >>> #765854
> > >>> ecryptfs cannot unmount encrypted home directories due to systemd keeping
> > >>> the pam session active even after logout.
> > >>> Upstream bug https://github.com/systemd/systemd/issues/8598
> > >>> A work around (user unit file) has not been implemented and tested.
> ...
> > > In absence of other text, I am about to push the attached text to the
> > > release-notes. I hope this isn't the final text, but at least the draft
> > > document now mentions the problem.
> >
> > Did anybody learn about (documented) migration paths in the mean time?
>
> Unencrypt eCryptfs data and mount the unencrypted filesystem is one way.
>
> But then we don't have encryption.
>
> I can think of migration to dm-crypt/LUKS or encfs/FUSE is an technical
> possibility. But that's something beyond this document should
> elaborate,
LUKS is the only sensible option, overlay file systems, especially
encfs are significantly less safe, which was among the reasons we
ended up here in the first place.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: