LWN: Comments on "Oniux: kernel-level Tor isolation for Linux applications" https://lwn.net/Articles/1021354/ This is a special feed containing comments posted to the individual LWN article titled "Oniux: kernel-level Tor isolation for Linux applications". en-us Sun, 02 Nov 2025 08:30:28 +0000 Sun, 02 Nov 2025 08:30:28 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net syd-tor is an alternative https://lwn.net/Articles/1021631/ https://lwn.net/Articles/1021631/ alip <div class="FormattedComment"> Syd's proxy sandboxing with syd-tor is an alternative for this using more or less the same method:<br> - Proxy sandboxing: <a href="https://man.exherbo.org/syd.7.html#Proxy_Sandboxing">https://man.exherbo.org/syd.7.html#Proxy_Sandboxing</a><br> - syd-tor: <a href="https://man.exherbo.org/syd-tor.1.html">https://man.exherbo.org/syd-tor.1.html</a><br> <p> PS: I am the main author of Syd.<br> </div> Mon, 19 May 2025 12:37:56 +0000 Leeks and leaks https://lwn.net/Articles/1021525/ https://lwn.net/Articles/1021525/ k3ninho <div class="FormattedComment"> I guess the Tor announcement could have said if they create the namespaces+cgroups with this environment variable applied to all processes inside, which sidesyep the issue and would also add clarity.<br> <p> K3n.<br> </div> Sat, 17 May 2025 08:40:18 +0000 Leeks and leaks https://lwn.net/Articles/1021518/ https://lwn.net/Articles/1021518/ Fowl <div class="FormattedComment"> Relevant post by Daniel Stenberg (of curl fame) about how this a bit of a reverse course for those apps that attempted to do the right thing with .onion in the past: <a href="https://daniel.haxx.se/blog/2025/05/16/leeks-and-leaks/">https://daniel.haxx.se/blog/2025/05/16/leeks-and-leaks/</a><br> </div> Sat, 17 May 2025 02:52:41 +0000 aarch64-unknown-linux-musl https://lwn.net/Articles/1021483/ https://lwn.net/Articles/1021483/ rillian <p>In case anyone else is confused building out of a local repo, the project <a href="https://gitlab.torproject.org/tpo/core/oniux/-/issues/6">is configured</a> to target <code>aarch64-unknown-linux-musl</code> by default, and will fail to build if cross-toolchains for that target are not installed. One can work around by passing <code>--target x86_64-unknown-linux-gnu</code> to cargo, or whatever one's native target is.</p> <p>The <code>build.target</code> directive in <code>.cargo/config</code> is ignored by <code>cargo install</code> which is why the blog post's suggestion of installing directly from the upstream repo works.</p> Fri, 16 May 2025 13:19:24 +0000