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-alpha-flashproxy-obfsproxy. 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 _______________________________________________ tor-dev mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
