Control: forwarded -1 https://github.com/rfjakob/gocryptfs/issues/550 Control: severity -1 important
Hi Matthias, On Sun, Mar 7, 2021 at 8:39 AM Matthias Jäger <matthias_jae...@gmx.net> wrote: > > the encrypted data was missing. Both upstream and I are stymied by your experience. I forwarded your report upstream [1] where you can find a response from Jakob. Since you are using the version in Debian stable, your issue is presumably present in all versions of gocryptfs and therefore best tracked upstream. Of course, you are still welcome to comment here. [1] https://github.com/rfjakob/gocryptfs/issues/550 > I'm using a gocryptfs container. It would be helpful if the bug could be reproduced—ideally, with version 1.8.0-1. > I can not be sure that this is caused by gocryptfs Your loss of data warrants the highest severity, but your report is about the stable version. Debian is currently in a release freeze, which means your filing is also severe enough to keep version 1.8.0-1 out of bullseye. Meanwhile, I have used gocryptfs without problems for several years in another complex setup (with kerberized NFSv4). We also do not know for sure, as you stated, that gocryptfs is at fault. For those reasons, I am downgrading this report to the highest non-RC level—at least until bullseye is released. Kind regards Felix Lechner
