Obfsproxy support for Tor Browser Launcher
I want to make it so Tor Browser Launcher users can optionally choose to install teh Obfsproxy TBB instead of the normal one, but I have some questions about that on this issue: https://github.com/micahflee/torbrowser-launcher/issues/38 Maybe someone here knows the answers. Here's the question: Do the obfsproxy bundles have the exact same release schedule as normal TBB? I know what the current alpha and stable version numbers are by looking here: https://check.torproject.org/RecommendedTBBVersions At the moment it seems like the current alpha is 2.4.11-alpha-2, and the obfsproxy bundle is at that same version too. Is it ever recommended to run the "stable" obfsproxy bundle? -- Micah Lee https://twitter.com/micahflee
On 16.04.2013 19:31, Micah Lee wrote:
Do the obfsproxy bundles have the exact same release schedule as normal TBB?
Unfortunately, no. Currently, obfsproxy bundles are built by different people with a different schedule.
At the moment it seems like the current alpha is 2.4.11-alpha-2, and the obfsproxy bundle is at that same version too. Is it ever recommended to run the "stable" obfsproxy bundle?
The current naming scheme was picked for the last release, releases before that used different schemes. You can only hope future releases follow the current scheme. I believe your best bet here is: Think about how you would want the interface to look like, and make it easy for future build people to follow that. The final goal is to not have separate bundles at all, so you should implement it in a way that separate bundles can easily be dropped (or added) in the future. -- Moritz Bartl https://www.torservers.net/
On Tue, 16 Apr 2013 19:54:30 +0200 Moritz Bartl <moritz@torservers.net> wrote:
I believe your best bet here is: Think about how you would want the interface to look like, and make it easy for future build people to follow that.
You can see this bug for a screenshot of what the settings dialog looks like so far: https://github.com/micahflee/torbrowser-launcher/issues/29 The "I prefer" dropdown has these options: * Tor Browser Bundle - stable * Tor Browser Bundle - alpha * Obfsproxy Tor Browser Bundle Right now it seems like the only way to tell what version of Obfsproxy TBB to download is by going here: https://www.torproject.org/projects/obfsproxy.html.en#download I'd rather not have Tor Browser Launcher make a GET request there and then try to parse. That's a very brittle approach and will break as soon as torproject.org gets redesigned, or even the layout of just that page changes. Would it be possible to include the current recommended obsfproxy version in this document? https://check.torproject.org/RecommendedTBBVersions That would make life way easier.
The final goal is to not have separate bundles at all, so you should implement it in a way that separate bundles can easily be dropped (or added) in the future.
That would be great! When that happens, Tor Browser Launcher can be simplified. -- Micah Lee https://twitter.com/micahflee
Micah Lee:
Would it be possible to include the current recommended obsfproxy version in this document? https://check.torproject.org/RecommendedTBBVersions
That would be related to <https://trac.torproject.org/projects/tor/ticket/8644> <https://trac.torproject.org/projects/tor/ticket/8645> -- Lunar <lunar@torproject.org>
On Tue, Apr 16, 2013 at 07:54:30PM +0200, Moritz Bartl wrote:
On 16.04.2013 19:31, Micah Lee wrote:
Do the obfsproxy bundles have the exact same release schedule as normal TBB?
Unfortunately, no. Currently, obfsproxy bundles are built by different people with a different schedule.
At the moment it seems like the current alpha is 2.4.11-alpha-2, and the obfsproxy bundle is at that same version too. Is it ever recommended to run the "stable" obfsproxy bundle?
The current naming scheme was picked for the last release, releases before that used different schemes. You can only hope future releases follow the current scheme.
I believe your best bet here is: Think about how you would want the interface to look like, and make it easy for future build people to follow that.
The final goal is to not have separate bundles at all, so you should implement it in a way that separate bundles can easily be dropped (or added) in the future.
What Moritz says is right. We're calling the obfsproxy bundles the pluggable transports bundles now: https://blog.torproject.org/blog/new-pluggable-transports-bundles-02411-alph.... My future plan for not having separate bundles is https://trac.torproject.org/projects/tor/ticket/8019#comment:3 I don't anticipate having stable pluggable transports bundles before the pluggable transport bundles become obsolete (i.e., become part of the standard browser bundle). David Fifield
participants (4)
-
David Fifield -
Lunar -
Micah Lee -
Moritz Bartl