#20844: Inform me about sandbox violations
----------------------------------------------+-------------------------
Reporter: arma | Owner: yawning
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser Sandbox | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------------------------------+-------------------------
Comment (by cypherpunks):
Replying to [comment:4 yawning]:
> Edit: I went and added a rule to SIGKILL on unexpected architecture (I
think it would have ENOSYSed), for the sake of my peace of mind.
I think libseccomp is supposed to automatically throw an error during the
initiation phase if they're running on the improper architecture. See
`seccomp_arch_exist(3)`.
In general, unless you're directly writing in raw BPF bytecode or writing
for multiple architectures at once, in the same seccomp running seccomp
filter, you don't have to worry about architecture issues.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20844#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
