Hi folks,
we have the issue that eCryptfs has not made it into Buster and has
fallen out of testing due to bug #765854.
To me it seems the most easy solution is from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854#107
as non-interactive logins don't have any passphrase to unlock an
encrypted home dir anyways.
Additionally we have #936465 now (Python2 dependency).
This is tracked upstream at
https://bugs.launchpad.net/ecryptfs/+bug/1871236
So questions:
@Martin, Dustin:
Is there still upstream support for eCryptfs?
I.e. will you resolve the LP bug linked above?
libecryptfs.py is just a SWIG generated wrapper.
So this probably trivial. But somebody that actually uses the
python-bindings would be needed to test.
Any comments on the best solution from the ones offered in Debian bug
#765854?
@Laszlo, Julian:
Do we want to get eCryptfs back into Bullseye so Stretch users can
upgrade there (or may be document a work-around with testing packages,
or we do a stable update for these folks)?
I'd really like to offer a solution to users of eCryptfs in Debian.
Some data from popcon:
Package Users
--------------- -----
ecryptfs-utils 1278
libecryptfs1 1122
python-ecryptfs 16
Kind regards,
Daniel
