Closed apyrgio closed 2 days ago
Actually, it seems that the underlying problem is that Tails has a more strict ptrace_scope
:
$ cat /proc/sys/kernel/yama/ptrace_scope
2
If I set the same scope in my Linux system, I see the same failure. There are some related issues in the gVisor tracker for this, e.g., https://github.com/google/gvisor/issues/9006. It looks though as if the problem was resolved.
I've notified the gVisor devs as well: https://github.com/google/gvisor/issues/11091
As an update on this topic, we've re-enabled DirectFS, in the 0.8.0
release. gVisor merged the changes we need, so when https://github.com/freedomofpress/dangerzone/issues/928 is solved, we should be able to solve this issue as well!
What happened?
I built a Debian package for the upcoming Dangerzone 0.8.0 release, and installed it on a Tails system. Dangerzone 0.7.1 in this Tails system works great. When I attempt to run the latest Dangerzone code there though, it fails.
Linux distribution
Dangerzone version
0.8.0 (from
main
branch)Podman info
Document conversion logs
Additional info
Performing the conversion with debug output returns the following debug log: dz-tails-crash.txt
The important line seems to be:
I also see this corresponding entry in
journalctl
:But more importantly, if I re-enable gVisor's DirectFS feature (which was disabled in https://github.com/freedomofpress/dangerzone/pull/898), the conversion works.