From: ng0 <ng0@infotropique.org>
To: Rutger Helling <rhelling@mykolab.com>, 27394@debbugs.gnu.org
Subject: [bug#27394] [PATCH] gnu: tor: Add seccomp support.
Date: Fri, 16 Jun 2017 22:09:02 +0000 [thread overview]
Message-ID: <20170616220902.agnoznv4nrcr7fdz@abyayala> (raw)
In-Reply-To: <20170616131008.deg2qeu7fzwwxnxy@abyayala>
There's a problem. I think it's not that problematic but it's a problem:
Activating the Sandbox option (torrc Sandbox 1) prevents reloading
certain functions of tor without stopping tor. Now when you do this
with our GuixSD tor-service running through a guix system reconfigure,
you will get a sandbox violation. Because I reboot directly after
reconfigure I don't know if this is a serious problem, but I know
there are plans for system-generation activation or what they call
it (switch to the newly generated system directly after it was build).
After a day of using your patch and encountering the sandbox violations
I'm positive it works as intended, but I'm not sure what to do about
the switch. Maybe our tor-service has to be adjusted? This is no
requirement for this to be merged, I'm just trying to point out details.
ng0 transcribed 1.8K bytes:
> The patch itself seems to work.
>
> Just introducing upstream explicitly marked (see 'man tor') as "experimental"
> features is difficult. As long as nothing breaks it's okay I guess.
>
> Should tor or the GuixSD native tor-service start to consume too much
> resources, we can still adjust.
>
> ng0 transcribed 2.3K bytes:
> > Rutger Helling transcribed 2.6K bytes:
> > > Hey ng0,
> > >
> > > I think that ticket references whether the default torrc should have
> > > "Sandbox 1".
> >
> > I understood the Whonix mail, which is how I got to the trac of tor,
> > in the way that they don't enable seccomp because tor does not enable
> > it as default. I'm not 100% positive on this, but I think I used
> > tor with +seccomp and hardening in Gentoo for a very long time.
> >
> >
> > > This patch doesn't do that, you still have to set that
> > > manually if you want to use it. It only gives you the option (Tor will
> > > just ignore that option in Guix right now).
> > >
> > > I also don't think that hardening and the sandbox bite each other in any
> > > way.
> > >
> > > On 2017-06-16 14:01, ng0 wrote:
> > >
> > > > Rutger Helling transcribed 2.5K bytes:
> > > >
> > > >> Hello,
> > > >>
> > > >> this patch adds seccomp support to tor.
> > > >
> > > > There's the question if we would want that.
> > > > tor doesn't enable it by default, see: https://trac.torproject.org/projects/tor/ticket/19215
> > > > But we also enable hardening by default, which differs from the tor default.
> > > > I have no problem with moving unstable features in, but hardening
> > > > seems much more tested to me than seccomp.
> >
> > --
> > ng0
> > OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> > https://krosos.org/~/ng0/ https://www.infotropique.org
>
>
>
> --
> ng0
> OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> https://krosos.org/~/ng0/ https://www.infotropique.org
>
>
>
>
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://krosos.org/~/ng0/ https://www.infotropique.org
next prev parent reply other threads:[~2017-06-16 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 11:21 [bug#27394] [PATCH] gnu: tor: Add seccomp support Rutger Helling
2017-06-16 12:01 ` ng0
2017-06-16 12:33 ` Rutger Helling
2017-06-16 12:46 ` ng0
2017-06-16 13:10 ` ng0
2017-06-16 22:09 ` ng0 [this message]
2017-06-20 21:07 ` bug#27394: " Ludovic Courtès
2017-06-20 22:31 ` [bug#27394] " ng0
2017-06-21 6:57 ` Rutger Helling
2017-06-21 8:24 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170616220902.agnoznv4nrcr7fdz@abyayala \
--to=ng0@infotropique.org \
--cc=27394@debbugs.gnu.org \
--cc=rhelling@mykolab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).