enable seccomp by default

Please consider enabling seccomp by default in tor-service-defaults.

changed milestone to %Tor: unspecified in legacy/trac

added component::core tor/tor in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac priority::medium in Legacy / Trac resolution::wontfix in Legacy / Trac severity::major in Legacy / Trac status::closed in Legacy / Trac type::enhancement in Legacy / Trac labels

I.e. add Sandbox 1 to /usr/share/tor/tor-service-defaults-torrc by default.

Can't do in 0.2.8; still not tested enough, and probably breaks some configurations.

Trac:
Keywords: N/A deleted, 029-proposed added
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.???

Trac:
Keywords: 029-proposed deleted, N/A added

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

There are enough cases where it just doesn't work that we can't do this.

Trac:
Resolution: N/A to wontfix
Status: new to closed

closed

moved from legacy/trac#19215 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label