From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Hardening (was: Re: tor: update to 0.2.9.9) Date: Wed, 25 Jan 2017 10:09:36 +0100 Message-ID: <87sho75wvj.fsf@elephly.net> References: <20170124111934.16080-1-contact.ng0@cryptolab.net> <20170124190726.GB6110@jasmine> <87bmuw2n3j.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <20170124210233.GB30771@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41346) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWJaU-0002NP-9z for guix-devel@gnu.org; Wed, 25 Jan 2017 04:09:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cWJaR-0000IP-1c for guix-devel@gnu.org; Wed, 25 Jan 2017 04:09:54 -0500 Received: from sender163-mail.zoho.com ([74.201.84.163]:21122) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cWJaQ-0000IH-OQ for guix-devel@gnu.org; Wed, 25 Jan 2017 04:09:50 -0500 In-reply-to: <20170124210233.GB30771@jasmine> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > On Tue, Jan 24, 2017 at 08:56:48PM +0000, ng0 wrote: >> Leo Famulari writes: >> > Should we build Tor with "--enable-expensive-hardening"? >> >> I will take a look later what can be applied other than the >> default configure flags. >> >> I'm all for hardening, but it seems that the first basic ideas >> for Guix are stuck in the idea state. > > As far as I can tell, --enable-expensive-hardening is specific to Tor, > so it's not relevant to the project of hardening all Guix packages. > >> It would be great to see some movement on this during this >> year. I volunteer to help with it, though I don't have as much >> experience with SELinux (and only basic experience with >> GrSecurity without a modular kernel like GuixSD uses). > > Yes, this effort needs a champion. I know SELinux and I have a couple of almost-ready packages for it. The bigger problem for us is writing SELinux policies, because we cannot just use those from Fedora. SELinux policies are applied to file paths (which are not stable in Guix) and are “remembered” using extended file attributes. This means we’d have to write policies that can deal with arbitrary prefixes and we’d have to add an optional service to automatically label all store items (that’s expensive but maybe it can be done incrementally). However, this is completely separate from enabling a configure flag for Tor. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net