[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-12-20 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 Damien Miller changed: What|Removed |Added Attachment #3641||ok?(dtuc...@dtucker.net)

[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-12-11 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 --- Comment #5 from Damien Miller --- Created attachment 3641 --> https://bugzilla.mindrot.org/attachment.cgi?id=3641=edit another version, logging via monitor Here'e another version, it's a bit more complex but it preserves logging via the

[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-12-11 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 Damien Miller changed: What|Removed |Added CC||d...@mindrot.org --- Comment #4 from

[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-10-03 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 --- Comment #3 from Darren Tucker --- (In reply to Colin Watson from comment #2) > (In reply to Darren Tucker from comment #1) > > [...]security vulnerabilities > > I don't think this is _not_ an issue, and I agree it requires care - > that's

[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-10-03 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 --- Comment #2 from Colin Watson --- (In reply to Darren Tucker from comment #1) > Arbitrarily failing syscalls that do not normally fail has been the > source of serious security vulnerabilities in the past (eg > CVE-2000-0506). That's why the

[Bug 3478] Default "kill" action of seccomp sandbox is fragile

2022-10-03 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3478 Darren Tucker changed: What|Removed |Added CC||dtuc...@dtucker.net --- Comment #1 from