Quote from: Derloda on November 05, 2021, 10:05:10 AM

Quote from: crypto_zoidberg on November 04, 2021, 09:59:58 AM

Yes, it will be enabled by default.

Awesome !

Quote from: crypto_zoidberg on November 04, 2021, 09:59:58 AM

We already got thin TOR library, you can take a look into it if you wish: https://github.com/hyle-team/tor-connect

Oh, I wasn't expecting a full reimplementation of the Tor stack. Is there any particular technical reason to do so that I am missing ?
Because there's so many ways it could go wrong : no padding, no guard rotation, no stream isolation, no pluggable transport for censorship resilience, nor every other crucial security/privacy features that Tor have implemented over time.

If this is only a matter of porting the Tor build process to CMake, which I believe has already been done by other projects, maybe it would be more interesting to go that way than reinventing the wheel ?

Other ToR implementations works as a resident process/daemon, which is not suitable for mobile application, we wanted to have light implementation which create "circle" and deliver tx to outer world. Also, tx itself is not something private - this info is absolutely public, so exit nodes won't hurt any privacy aspects of transaction, only if someone can re-construct full circle of onion route and figure out ip address, which i guess quite hard with ToR.