Hello,
We decided to deactivate and finally remove EncFS from Back In Time
gradually over the next five years in a user-friendly manner.
There is a Meta-Issue about the details, reasons and time plan [1].
We warmly invite you to participate in the process by providing feedback
and suggestions on how to proceed and highlighting any potential issues
we may not have considered.
Beside the details one main point of discussion is not finally decided.
We appreciate if you would give us feedback and your thoughts about it.
In the current state of discussion it is preferred not to replace EncFS
with an alternative library (e.g. GoCrypt) but to use encryption on file
system level (e.g. LUKS) and improve BIT in a way to easier handle file
systems like this. The discussion started in a previous thread here in
the mailing list [2].
Beside the Meta-Issue [1] mentioned there are two open issues related to
the first step in this process. One is about formulating the deprecation
warnings and information for the users [3]. The other is about doing
research if we need to and how we can improve BIT to handle encrypted
file systems (e.g. LUKS) managed by the operating system [4].
[1] -- <https://github.com/bit-team/backintime/issues/1734>
[2] --
<https://mail.python.org/archives/list/[email protected]/message/D2GXCCVUAVZ2E5ELBHUZGT7ITUN4ADEP/>
[3] -- <https://github.com/bit-team/backintime/issues/1735>
[4] -- <https://github.com/bit-team/backintime/issues/1736>
_______________________________________________
Bit-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/bit-dev.python.org/
Member address: [email protected]
