<div>Jacob wrote:</div>> That sorta seems like a risky proposition, no?<div><br></div><div>In what way?</div><div><br><div>> Do you integrate Torbutton or something like it in some way?</div><div><br></div><div>It works more like Freecap but I've added the code directly to the Firefox socket code.</div>
<div><br></div><div>> Additionally, if Firefox only talks to Tor, do you have a control port open?</div><div><br></div><div>No, only the socks port 9060 (non-default) is open.</div><div><br></div><div>> I assume I'd just find the matching files in Firefox 3.0.10 and clobber<br>
them with your files?<br><br></div><div>That's right.</div><div><br></div><div>> How does someone replicate your builds on <a href="http://torfox.org" target="_blank">torfox.org</a>? Do you plan on<br>publishing that too? Perhaps it would be useful to have a README.build<br>
with patching and building information?</div><div><br></div><div>After you replace the files you can build Firefox normally. Other than those 3 source code files in the SVN I've only changed the branding stuff and startup options. I just search and replace the string "firefox" with "torfox" and I have some icons and graphics I've made. I have some parts I need to automate but I will definitely add a build section and the branding stuff for building from source. </div>
<div><br></div><div>> It seems like you're not getting much more over the current Tor Browser Bundle. Additionally, do you take into account the non-Torbutton protection and usability improvements that we have added?</div>
<div><br></div><div>I think it just appeals to a different style of usage. That's the reason I wanted to make it anyways. I've disabled Java, set it to auto delete private data on shutdown, etc. I'm looking for input as far as what kinds of protection needs to be added.</div>
</div>