Hello,

EncFS support in Back In Time will be removed much earlier than
previously planned [1]. Monitor the progress in this PR #2449 [2].

Recent development work on the implementation of gocryptfs support
revealed that maintaining EncFS in parallel introduce significant
complexity and maintenance overhead. Continuing to keep EncFS in the
code base would block progress on gocryptfs and jeopardize the entire
plan.

I have decided to remove the complete mounting logic and re-implement
it from scratch. Refactoring the existing EncFS logic would consume
disproportionate time and effort for a component that is scheduled for
removal.

As a consequence, EncFS must be removed before gocryptfs can be fully
implemented.

The original plan was to add full gocryptfs support and release that
verison of Back In Time with the upcoming Debian 14 (~end of 2027),
removing EncFS afterwards. This is no longer feasable. The version of
Back In Time version for Debian 14 will include full gocryptfs support
will not longer support EncFS.

Users currently relying on EncFS should start planning a migration to
gocryptfs. Migration documentation and guidance will be provided.
Additionally, there is the plan to ensure that the latest
EncFS-supporting version of Back In Time remain usable on Debian 14,
when installed from upstream.

Please let me add that the security issues with EncFS are known since
the year 2014 [3]. Removing it from Back In Time was decided in 2023,
and first deprecation warning within Back In Time was released in July
2024 with version 1.5.0 [4].

Best regards,
Christian Buhtz
Current maintainer & lead developer

[1] https://github.com/bit-team/backintime/issues/1734
[2] https://github.com/bit-team/backintime/pull/2449
[3] https://sourceforge.net/p/encfs/mailman/message/31849549/
[4] https://github.com/bit-team/backintime/releases/tag/v1.5.0
_______________________________________________
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]

Reply via email to