Nice, now please rewrite the prototype in C and will happily use it.
Oniux: Kernel-level Tor isolation for any Linux app
31–40 of 54 posts
Re: Oniux: Kernel-level Tor isolation for any Linux app
#32Does this mean one can now access tor websites using chrome?
You always could by just setting the proxy environment variables (or in settings). The standard port for the tor daemon is 9050. In fact, it's relatively easy to write a socks proxy that lets you route traffic through a arbitrary protocols. For example, I can serve/visit websites on syncthing with a socks5 proxy as a translation layer: https://github.com/acheong08/syndicate
Re: Oniux: Kernel-level Tor isolation for any Linux app
#33Isn't all this reserved to TCP, in other words in which way may it protect non-TCP activity?
Non-TCP activity wouldn't route and will fail to send.
Re: Oniux: Kernel-level Tor isolation for any Linux app
#34Re: Oniux: Kernel-level Tor isolation for any Linux app
#35Isn't all this reserved to TCP, in other words in which way may it protect non-TCP activity?
Non-TCP activity wouldn't route and will fail to send.
Maybe I'm wrong, but it seems similar to I2P where if you want "UDP", you'd need bespoke plugins/transports/whatever for each application.
Re: Oniux: Kernel-level Tor isolation for any Linux app
#36Earlier quoted context omitted.
Non-TCP activity wouldn't route and will fail to send.
Thank you, therefore my first impression seems right: without any provision for UDP this isn't an easy-to-setup and transparent way for any user to preserve his/her privacy.
Users who try to do a lot of UDP traffic will have to change their habits, yes. But a majority of users who don't know a lot about computers rarely do anything on a PC that isn't driven by the browser anyway.
But at least the users who try to use UDP won't wind up specifically leaking info, just wind up slightly confused why certain things aren't working.
Re: Oniux: Kernel-level Tor isolation for any Linux app
#37Huh. I had a conversation with a Tor developer on this topic about a decade ago, when network namespaces were still kind of a new hotness - the feedback I got was that it would be an easy way for people to think they were being secure while still leaking a bunch of identifiable information, so I didn't push that any further.
Strange, because torsock and torify do the same thing, but less robustly.
Using tor directly on the kernel level means that your DNS is gonna leak. Your OS telemetry is gonna leak etc.
It's still a good idea but it should be implemented top to bottom and nothing left in between, otherwise you're de-anonymized quickly.
Re: Oniux: Kernel-level Tor isolation for any Linux app
#38Re: Oniux: Kernel-level Tor isolation for any Linux app
#39Huh. I had a conversation with a Tor developer on this topic about a decade ago, when network namespaces were still kind of a new hotness - the feedback I got was that it would be an easy way for people to think they were being secure while still leaking a bunch of identifiable information, so I didn't push that any further.
Re: Oniux: Kernel-level Tor isolation for any Linux app
#40 cargo install --git https://gitlab.torproject.org/tpo/core/oniux oniux@0.5.0