So, the tor project maintains their own fork of firefox in the tor browser bundle. I know that there have been efforts to try to merge their changes into our repos. AFAIK, the main reason we haven't done so is because some of their changes modify the default behavior of firefox.
As a side note, I have a working b2g build of libevent, openssl + engines, and the tor daemon (all static). I'm in the process of setting up the a good manifest so that others can recreate it. It won't be buildable out of the box if you just clone my repos until I set up the manifest correctly. But I've completed all of the work making Android.mk files so that the three pieces build as b2g/external/*. If anybody wants to take a look/help, my repos are here: github.com/dhuseby All of my changes are in b2g branches in the libevent, openssl, and tor forks. -dave On 08/08/2013 09:48 AM, Sid Stamm wrote: > On 8/8/13 8:52 AM, Bernard Tyers - ei8fdb wrote: >> "Maybe we should just adopt, support, and bundle Tor in Firefox..." >> [1] >> >> It's early days, and just a comment on Twitter, but I wonder what >> others have to say. >> >> Good or bad idea? I would say (without too much thinking): turned-off >> by default, but available. Exciting possibilities. > > Let me turn it around: what do you think? Why would you like to see this? > > I think it's interesting, and at the very least we could work more > closely with the Tor engineers to make each others software better. > > -Sid > _______________________________________________ > dev-privacy mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-privacy >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-privacy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-privacy
