Received: by 10.223.164.202 with SMTP id h10csp309843wrb; Wed, 29 Nov 2017 22:53:16 -0800 (PST) X-Google-Smtp-Source: AGs4zMZB6Dtl6JsStaH1Pf4gdpOo9CYaEhThZAgUNG4rKEkm68nY1z5++KQHnjMAltUP3BVshtpM X-Received: by 10.84.132.34 with SMTP id 31mr1533822ple.395.1512024795904; Wed, 29 Nov 2017 22:53:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1512024795; cv=none; d=google.com; s=arc-20160816; b=fr+qrfhBENjo+S4mkBAyMzOjIDfO8ipTLJvdU013WofEn9zTp6Dp46fMh7pX/cvKP8 Y1BlHnL0bntO8G4xeKDOGCKlZ+tp5DBOvVPq45XCYd6WGt/WkmH/ixYASKcHBiRSzJj6 PnbK5IXqJVAutEskWbeMRyNpSZdGKcrNopqc6jCWataZBpKROS9Gum9HQxNYeVowSv8r PfWwNj6c97C8nBXbZXruS22OBTFFsYygyqWBbGvnrHKqx+uqxcRVs6bqq20Om06nLICZ jyU0X3QZaZPmQ4B7FOaX6N/4/0hNkwQiEbBeT+WcLuXRLNC4ZTS9pMx4YQ2cntMWo8zV 3W8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature:arc-authentication-results; bh=2MXpeMjJwhvrmjUC6Nb36o5oXDYapoxzUtv4cTSgCGE=; b=siTeu6RTKuDUC4grJYoCRwGCplF+7WYD71enpArnRlbq1pQIsaHNIgusOasBW1mu0O ea/ssP2POLsLcmHp0V9ZcscI981QWVIdfwX9qMAWM/Or2jiae1YprWQCBS5pb/5oYcbD DTcIqBHmUeySkfB6OkxV7CSYJr9EQrXwb6x8AovGKeFXtovIIWyrthwMEog+MtFK3AwX GX39rlbT83yCS7KKlvprXyWpt44O9hfsnkSyFgXydg/vDyOTuaJxWLTpbQsHOqStCIkP 5abN76OSJbbBWBbldHHPMAFlmPdIi6HfPkNcA0I6WPAlUmGPaFjC2QE4IzlC5q0DgOTd Mcmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Kc7pvtbj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y34si2606325plb.319.2017.11.29.22.53.01; Wed, 29 Nov 2017 22:53:15 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Kc7pvtbj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752398AbdK3GvW (ORCPT + 99 others); Thu, 30 Nov 2017 01:51:22 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:46590 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbdK3GvU (ORCPT ); Thu, 30 Nov 2017 01:51:20 -0500 Received: by mail-it0-f67.google.com with SMTP id t1so7057803ite.5; Wed, 29 Nov 2017 22:51:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=2MXpeMjJwhvrmjUC6Nb36o5oXDYapoxzUtv4cTSgCGE=; b=Kc7pvtbj+3LNd2UFm9ybFtLtO0I+nd/obKW7hgoBChfSo0UjkKwT1GwJauopDVldnJ rkdbphjUdU2xdv9I05wHVU//HfMkGNKz+q0bsebG2KMsCR3SYlN4Xd4bn3xh18mZjBlz wgDZv5imhifWFw/cBaHEvLb1OiPoHwFij0xGuwBFfnlXWR2SmEzOsdbV6Q5doU7Lrpgf gjI6pdKbnABvLvFHS58HXIqf3tmHqt3JBLTCM6Av7/9r8OINpsas9XrcA+ojaTCXqQPm xfhLQrxa1YKc7CVqsJAI4m0R+G+QJ+U6zWQgn8s3J8N/1Dks254oeLSrlYtbi7VTsZTo 5f9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=2MXpeMjJwhvrmjUC6Nb36o5oXDYapoxzUtv4cTSgCGE=; b=c2vMXbjpjAkj3K6699O3/95Gjnd63+WjbIep4T3SV6KXwzmOxEAycEcEtNAWxYTpmC wMEVxwqIEWOSslg7yNPNE5roJ8gr8blQDNDpuDh0e6AswAUEXKID+9jTJkfUOMIDr9AO QQoisu6F3SbPrDR5cgEm8K5EaO3tyLD44o/bK+Aqi2Yr4GJv8KyjrDOEYsX+rbZT6ujM FF3ag0uYmz1yajmGFtr/A4b3Hj8MKCqcRUwL35FuI4hHfUTzOflayYe5smpqdYq4KBFn XGPWzlxfS1gPl+p/jNZ/cQcLR+zPf8PAVJT71QpRE8BtH/yc8ORtNZmmUysJU2SJPBer 1pOQ== X-Gm-Message-State: AJaThX4iXIxydx5ToLO1U/TGTthcFKnxD5RFVd2SEv1KhBY9o6BriAYo ca/JaX7HfqlnwtMLfvJkArw= X-Received: by 10.36.69.101 with SMTP id y98mr1941657ita.35.1512024679371; Wed, 29 Nov 2017 22:51:19 -0800 (PST) Received: from thinktank ([2607:fea8:59f:fec5::4]) by smtp.googlemail.com with ESMTPSA id i201sm1934893ita.32.2017.11.29.22.51.17 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 29 Nov 2017 22:51:18 -0800 (PST) Message-ID: <1512024677.1374.168.camel@gmail.com> Subject: Re: [kernel-hardening] Re: [PATCH v5 next 5/5] net: modules: use request_module_cap() to load 'netdev-%s' modules From: Daniel Micay To: Linus Torvalds , Kees Cook Cc: Djalal Harouni , Jessica Yu , LSM List , Linux Kernel Mailing List , "kernel-hardening@lists.openwall.com" Date: Thu, 30 Nov 2017 01:51:17 -0500 In-Reply-To: References: <1511803118-2552-1-git-send-email-tixxdz@gmail.com> <1511803118-2552-6-git-send-email-tixxdz@gmail.com> <1100603534.56586.1511871419952@ichabod.co-bxl> <20171128193243.4fymnjk7fplqw62x@thunk.org> <708003731.69563.1511905898471@ichabod.co-bxl> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > And once you disable it by default, and it becomes purely opt-in, that > means that nothing will change for most cases. Some embedded people > that do their own thing (ie Android) might change, but normal > distributions probably won't. > > Yes, Android may be 99% of the users, and yes, the embedded world in > general needs to be secure, but I'd still like this to be something > that helps _everybody_. Android devices won't get much benefit since they ship a tiny set of modules chosen for the device. The kernels already get very stripped down to the bare minimum vs. enabling every feature and driver available and shipping it all by default on a traditional distribution. Lots of potential module attack surface also gets eliminated by default via their SELinux whitelists for /dev, /sys, /proc, debugfs, ioctl commands, etc. The global seccomp whitelist might be relevant in some cases too. Android devices like to build everything into the kernel too, so even if they weren't using a module this feature wouldn't usually help them. It would need to work like this existing sysctl: net.ipv4.tcp_available_congestion_control = cubic reno lp i.e. whitelists for functionality offered by the modules, not just whether they can be loaded. From 1585455038844237366@xxx Thu Nov 30 02:09:10 +0000 2017 X-GM-THRID: 1585240629942062556 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread