<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 20, 2015, at 12:15 PM, Georg Koppen <<a href="mailto:gk@torproject.org" class="">gk@torproject.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Nathan Freitas:<br class=""><blockquote type="cite" class=""><br class="">Amogh and I are trying to figure out the shortest path to getting<br class="">TorButton ported to Android, such that we can have the essential privacy<br class="">features without having to say, port all the XUl/user interface<br class="">components.<br class=""><br class="">Our plan is to remove all XUL components (for now) since those would<br class="">need to be written for the mobile specific XUL on Android, and they seem<br class="">to be helpful but not absolutely required.<br class=""></blockquote><br class="">I don't think this is true. "New Identity" comes to mind which does not<br class="">work if you just remove all XUL related things. Window resizing/Screen<br class="">size spoofing is another feature. And there are probably a bunch of<br class="">others as well.<br class=""></div></blockquote><div><br class=""></div>The “New Identity” feature can be replaced for mobile, since Orbot handles all the tor connections, I think it would be possible to add this functionality through NetCipher’s OrbotHelper class[0]. </div><div><br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">From there, hopefully all the code here:<br class=""></blockquote><a href="https://gitweb.torproject.org/torbutton.git/tree/src/components" class="">https://gitweb.torproject.org/torbutton.git/tree/src/components</a><br class=""><br class="">should work in the mobile context. However, there could be problems<br class="">based on not all of the JS/DOM API being the same. Since we also don't<br class="">run our own instance of Tor within Orfox, none of the control port<br class="">specific JS is relevant.<br class=""><br class="">If anyone on this list can help us prioritize the JS components to<br class="">required vs nice to have, that would be helpful.<br class=""></blockquote><br class="">See the "Bug 1506 PX" comments where the "X" is in the range of 0-5 (0 =<br class="">low prio, 5 = high prio) which got included a while a ago. This is,<br class="">however, missing the latest Torbutton improvements. But it might be a<br class="">good start and we could use the momentum to categorize the newer code<br class="">accordingly as well.<br class=""></blockquote><div><br class=""></div>Much of the extra control port JS could be modified to talk to the Java layer which communicates with Orbot which in turn handles these connections. This is a lot of work though, might be a good idea but.<br class=""><br class=""></div><div>Best,</div><div>amoghbl1</div><div>[0] <a href="https://github.com/guardianproject/NetCipher/blob/master/libnetcipher/src/info/guardianproject/netcipher/proxy/OrbotHelper.java" class="">https://github.com/guardianproject/NetCipher/blob/master/libnetcipher/src/info/guardianproject/netcipher/proxy/OrbotHelper.java</a></div><div><br class=""></div><div><br class=""></div></body></html>