As I mentioned in the ticket, you need to run > ndk-build in the
/orbotservice directory to create those native assets first.
We are working on extracting the native binary build components into a
separate gradle dependency, to make working on the app itself, easier.
For now though, yes, you must
It's hard to build Orbot, I solved several problems with the toolchain but
now I'm stuck here building Tor binary:
zip ../orbotservice/src/main/assets/armeabi/pdnsd.mp3
../orbotservice/src/main/libs/armeabi/pdnsd
zip warning: name not matched:
../orbotservice/src/main/libs/armeabi/pdnsd
zip
I think it would work like the start/status intents that are currently
in Orbot. The app sends an Intent to Orbot to request a Hidden Service
to be created, then Orbot sends reply status Intents to the app that
made the request with all relevant info, including a FileProvider URI
with GRANT URI
What do you think about the most obvious approach?
Use public intents than any other app can call to create/delete a hidden
service or for get config files of his service?
2016-11-15 15:17 GMT+01:00 arrase :
> Are you suggesting something? XD
>
> I can take a look at the
Are you suggesting something? XD
I can take a look at the problem and propose a solution, it will not be
fast but I can do it.
Tonight I will try to compile Orbot from sources and try to familiarize
myself with the code. (Is there a wiki with info??)
How do you want to focus the change? What
Might be of interest to some on this list, I aim to be there since its
in my home town. It unfortunately overlaps with the Internet Freedom
Festival in Valencia.
Original-Nachricht
Betreff: Android Security Symposium: 8-10 March 2017 in Vienna, Austria
Datum: Thu, 10 Nov 2016
2016-11-15 13:23 GMT+01:00 Michael Rogers :
> Hi arrase,
>
> Thanks for discovering this bug. Can you describe how Briar's Tor daemon
> conflicts with Orbot? What problems does it cause? Our goal is for Briar
> to be able to operate on the same device as Orbot without
Hi arrase,
Thanks for discovering this bug. Can you describe how Briar's Tor daemon
conflicts with Orbot? What problems does it cause? Our goal is for Briar
to be able to operate on the same device as Orbot without problems.
Thanks,
Michael
On 15/11/16 00:32, arrase wrote:
> I have reviewed the