[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6396 [Tor Bridge]: Reachability tests for obfuscated bridges
#6396: Reachability tests for obfuscated bridges
------------------------+---------------------------------------------------
Reporter: asn | Owner:
Type: task | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor Bridge | Version:
Keywords: pt | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Changes (by isis):
* cc: isis@â (added)
Comment:
I've created an OONI ticket #6804 for this, and it is being added to the
bridge reachability test #6414.
The way I have designed it thus far, it will work by doing:
{{{
$ ./ooniprobe.py bridget --bridges=bridge_ip_orport_list.txt \
--transport='obfs2 exec /usr/local/bin/obfsproxy --managed'
}}}
exactly as one would set the ClientTransportPlugin string in a torrc.
Will that work? Is there anything else which would be helpful, like any
other torrc strings which should be set, or maybe parsing a file of extra
torrc options?
Also, because OONI and the bridge reachability tests are using txtorcon,
and the spawned Tor calls exec, I am wondering what kinds of extra
security checks I should use to make sure that exec doesn't get abused. If
there isn't a way to make that safe, I will just include this option in
the bridge reachability test in a separate repo, and not in the main OONI
bridget test.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6396#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs