Bug#1015151: firejail: (Regression) Segfault when using --net=$namespace

Package: firejail Followup-For: Bug #1015151 X-Debbugs-Cc: debbug.1015...@sideload.33mail.com I did another test, this time ensuring that the profile was read: $ firejail --net=vnet0 --dns="$(ip address show dev vnet0 | awk '/inet\>/{gsub(/[/].*/,""); print $2 }')"\ --profile=<(pr

Bug#1015151: firejail: (Regression) Segfault when using --net=$namespace

Package: firejail Followup-For: Bug #1015151 X-Debbugs-Cc: debbug.1015...@sideload.33mail.com I tried the suggestion and it made no difference, but I suspect I have a separate problem with local profiles. I first looked through the man page for a commandline equivalent to “ignore noroot” and foun

Bug#1015151: firejail: (Regression) Segfault when using --net=$namespace

Package: firejail Followup-For: Bug #1015151 X-Debbugs-Cc: debbug.1015...@sideload.33mail.com When doing this upgrade: 0.9.64.4-2 → 0.9.64.4-2+deb11u1 ~50+ or so other packages were upgraded at the same time which could have theoretically changed the Tor middlebox. So more testing was needed t

Bug#1015151: firejail: (Regression) Segfault when using --net=$namespace

Package: firejail Version: 0.9.64.4-2+deb11u1 Severity: important X-Debbugs-Cc: debbug.firej...@sideload.33mail.com, t...@security.debian.org This upgrade introduced a segmentation fault: firejail:amd64 0.9.64.4-2 → 0.9.64.4-2+deb11u1 This is a sample command where it fails: $ firejail --ne