From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNRgs-0000qo-RS for guix-patches@gnu.org; Tue, 20 Jun 2017 18:32:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dNRgo-0008Is-Qr for guix-patches@gnu.org; Tue, 20 Jun 2017 18:32:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:55917) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dNRgo-0008Ik-NH for guix-patches@gnu.org; Tue, 20 Jun 2017 18:32:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dNRgo-0004gY-E2 for guix-patches@gnu.org; Tue, 20 Jun 2017 18:32:02 -0400 Subject: [bug#27394] [PATCH] gnu: tor: Add seccomp support. References: Resent-Message-ID: Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 From: Date: Wed, 21 Jun 2017 00:31:18 +0200 (CEST) In-Reply-To: <87bmpil65h.fsf@gnu.org> Message-Id: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 27394-done <27394-done@debbugs.gnu.org>, Rutger Helling On Tue, 20 Jun 2017 23:07:38 +0200, ludo@gnu.org (Ludovic Court=C3=A8s) wro= te: > Hi Rutger, >=20 > Rutger Helling skribis: >=20 > > From 5e93733bba145ac3e3a3f39fb43f25ad7125fa2f Mon Sep 17 00:00:00 2001 > > From: Rutger Helling > > Date: Fri, 16 Jun 2017 13:15:17 +0200 > > Subject: [PATCH] gnu: tor: Add seccomp support. > > > > * gnu/packages/tor.scm (tor)[inputs]: Add libseccomp. >=20 > Applied, thanks. >=20 > Do you think the GuixSD service should set =E2=80=9CSandbox 1=E2=80=9D by= default? The > Besides, the GuixSD service runs Tor in a container, but that doesn=E2=80= =99t > necessarily provide the same guarantees: > . >=20 > Ludo=E2=80=99. As mentioned earlier in the thread: I don't think it should be default unti= l we have found it to be stable enough. I experienced several "sandbox violations" wh= en running this in the last days. Is this good? Is this bad? I had no chance to invest= igate this so far. It also goes against torproject recommendations, as they consider sandbox (= seccomp) in tor to be an unstable + testing feature, disabled by default.