Opened 2 years ago

Last modified 3 months ago

#23378 new enhancement

Call "Sandbox 1" no longer an experimental feature?

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now the man page says that Sandbox is an experimental feature.

What needs to happen for us to stop calling it experimental?

We should sort out a roadmap and then we can know when we've gotten there.

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by nickm

Milestone: Tor: 0.3.3.x-final

In my opinion, we can change it from "experimental" to "linux-only".

comment:2 Changed 23 months ago by nickm

We should also be clear that not every feature will work with it, and that it's going to suddenly stop working when your libc decides to use new syscalls.

comment:3 Changed 20 months ago by dgoulet

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

Moving a bunch of tickets from 033 to 034.

comment:4 Changed 18 months ago by nickm

Keywords: 034-triage-20180328 added

comment:5 Changed 18 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:6 Changed 18 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:7 Changed 3 months ago by cypherpunks

i compile debian tor from source. i cannot use i get:

This version of Tor was built without support for sandboxing. To build with support for sandboxing on Linux, you must have libseccomp and its necessary header files (e.g. seccomp.h).
apt install libseccomp-dev libseccomp2 seccomp

just missing needed libs. But starting fails? (Sandbox) Caught a bad syscall attempt (syscall 289)

Note: See TracTickets for help on using tickets.