#20782: Use a seccomp whitelist when the tor daemon is configured to use
Bridges.
----------------------------------------------+-------------------------
Reporter: yawning | Owner: yawning
Type: enhancement | Status: closed
Priority: High | Milestone:
Component: Applications/Tor Browser Sandbox | Version:
Severity: Normal | Resolution: fixed
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------------------------------+-------------------------
Changes (by yawning):
* status: new => closed
* resolution: => fixed
Comment:
https://gitweb.torproject.org/tor-browser/sandboxed-tor-
browser.git/commit/?id=7cf5fba78a7641043454f7f7d24edce4ed938197
For now use a combined tor + obfs4prxy whitelist. Seems to work in my
test envs. I'm going to tag this as fixed for now, and deal with
decoupling the two later.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20782#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
