You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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., google/gvisor#9006. It looks though as if the problem was resolved.
This reverts commit 73b0f8b.
Unfortunately, disabling DirectFS causes a problem in Linux systems that
enable Yama mode 2. Turns out that Tails is such a system, so we have to
revert this change, if we want to support it.
Refs #982
This reverts commit 73b0f8b.
Unfortunately, disabling DirectFS causes a problem in Linux systems that
enable Yama mode 2. Turns out that Tails is such a system, so we have to
revert this change, if we want to support it.
Refs #982
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 #898), the conversion works.
The text was updated successfully, but these errors were encountered: