-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current version broken in Tails #179
Comments
Here's the crash:
Here's the tor log during the crash:
|
This looks like an upstream Tor bug. I've confirmed that this happens only happens when tor is in sandbox mode, which is now the default setting for Tails (but not for Tor Browser -- in fact tor crashes immediately when running Tor Browser if it's in sandbox mode). Here's the docs for sandbox mode:
I'm about to build a simpler script to reproduce this and open an upstream tor bug. |
Here's the upstream tor bug: https://trac.torproject.org/projects/tor/ticket/16106 I've changed this issue to blocked because I don't think it can get resolved until it gets fixed upstream, or unless Tails decides to run Tor unsandboxed. |
I'm removing the 0.7 milestone from here because I want to go ahead and release 0.7, and hopefully this is just an upstream bug anyway so there won't be any code changes in onionshare to resolve it. |
It looks like the reason the sandbox crashes is because it's trying to read/write from a place in the filesystem it's not allowed to. Tor might fix the bug so that this throws a warning instead of crashing. But now this issue is blocked until I can implement #178, so that I can start a HS without needing to access the filesystem. And that issue can't be complete and released until Tor 0.2.7.1 is stable and released as part of Tor Browser. |
Tor Browser bundle is now at 5.0.2, which ships with Tor 0.2.7.7. |
Merging with #220 |
In Tails when you start the server it launches a separate root process. In the current version in Tails it gives the error "Unknown error with Tails root process".
The text was updated successfully, but these errors were encountered: