Hello, thanks @Jakob for pointing out the upstream issue.
Is there any plan to backport the fix into Debian stretch? The issue is quite annoying and downgrading or using the package from sid/buster feels uncomfortable. Upstream issue 214 [1] is marked as duplicate of 348. There [2] you can find the link to a fix [3]. That specific commit is not part of the 1.9.2 release, but if you look on the compare page [4] for v1.9.1 to v1.9.2 in the official repository, then you can find the fix [5] that was actually shipped in the 1.9.2 release. So for a potential backport, you should consider [5]. Or is there any chance to get 1.9.2 into stable-proposed-updates? [1]: https://github.com/vgough/encfs/issues/214 [2]: https://github.com/vgough/encfs/issues/348#issuecomment-317240681 [3]: https://github.com/rfjakob/encfs-next/commit/990631be9f53c861d54492bba884d6b9c1a7cec5 [4]: https://github.com/vgough/encfs/compare/v1.9.1...v1.9.2 [5]: https://github.com/vgough/encfs/commit/e2f0f8e3c68604a46d8665c3b0125bb35a0d9181 Thanks! Sebastian
