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.
>
>> * what would be the alternative(s) available in buster
> there is none
Does Debian really not provide any alternative mechanisms for
filesystem encryption that users could switch over to? A quick "apt
search" suggests that they could try encfs...
>> * is there a (documented) migration path
> there is none
Sounds as if someone needs to write one, then.
> People with ecryptfs should not upgrade to Buster or enable and pin sid
> repositories where ecryptfs-utils, libecryptfs1 and friends are still
> available and continue to work (including the unmount bug linked above).
Is the problem a result of changes in ecryptfs-utils, PAM, systemd, or
what? Would upgrading systemd etc to Buster but keeping the Stretch
version of ecryptfs-utils installed be a better or worse option than
installing the Sid version?
> CC'd jak (original bug submitter) and gcs (maintainer) in case they can add
> something. May be we can get the user unit file approach tested and if
> working into a point release and/or backports?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
