[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5011 [Pluggable transport]: Discuss possible designs for an external program that discovers bridge addresses to tell Tor about them
#5011: Discuss possible designs for an external program that discovers bridge
addresses to tell Tor about them
---------------------------------+------------------------------------------
Reporter: karsten | Owner: mikeperry
Type: task | Status: new
Priority: normal | Milestone: Sponsor F: March 15, 2012
Component: Pluggable transport | Version:
Keywords: | Parent: #5010
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by mikeperry):
How does Option 4 bootstrap before the user can use TBB? Without Tor
access working, Torbutton won't see anything...
Why is Option 3 of making BridgeFinger a controller not worth it? Along
the lines of what rransom said, it seems simpler if this pattern can be
used for any type of pluggable transport by directly configuring tor.
If we go with Option 3, we could also create a form of IPC that flows
through Tor. Ie: Some browser plugin you have that knows about Tor sees
the string in a page. It tells tor to post an event. The BridgeFinger sees
the event, does its magic, and then setconfs Tor. I suspect that
centralizing the IPC around Tor will avoid us having to deal with multiple
IPC mechanisms and ugly situations where everyone is trying to talk to
everyone else and it's not clear who failed.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5011#comment:4>
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