On Sun, Jul 14, 2019 at 01:27:59PM +0200, Martin Steigerwald wrote:
> Hendrik Boom - 13.07.19, 01:01:
> > On Fri, Jul 12, 2019 at 01:33:22PM -0400, Steve Litt wrote:
> > > On Fri, 12 Jul 2019 12:00:35 -0400
> > >
> > > Hendrik Boom <hendrik@???> wrote:
> > > > Debian actually removed one of the encrypted file systems because
> > > > it turns out to be incompatible with systemd.
> > >
> > > Are you absolutely positive this is true? I was unable to find such
> > > a thing with a 10 minute web search. Could you please tell us the
> > > name of the encrypted filesystem and a URL describing the removal?
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854
> >
> > Debian Bug report logs - #765854
> > ecryptfs-utils: Private directory not automatically unmounted anymore
> > on logout
> >
> > It seems there's poor interaction between ecryptfs-utils and user
> > logout. Specifically, that the encrypted volume remains mounted.
> > There's a long discussion how to tweak it and systemd to make it work,
> > and it looks like they eventually just gave up.
> >
> > Maybe someone else can understand th problem in more detail than I
> > can.
> >
> > The remocal is mentioned in section 5.1.9. Noteworthy obsolete
> > packages,
> > https://www.debian.org/releases/stable/amd64/release-notes/ch-informa
> > tion.en.html#noteworthy-obsolete-packages
>
> Whoa, I am using ecryptfs.
>
> I still have ecryptfs-utils, but that is due to using Debian Unstable
> aka Sid.
>
> Not digging deeper into this at the moment, just telling: That with
> sysvinit the ecryptfs directory gets unmounted *just fine* :)
>
> So I believe Beowulf could just ship ecryptfs-utils, no matter whether
> it is shipped for Debian Buster or not.

Yes, we probably should. But we might have to us the real upstream source
and not Debian.

-- hendrik