Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp418141pxu; Sun, 22 Nov 2020 13:10:13 -0800 (PST) X-Google-Smtp-Source: ABdhPJxOIcrVHK6m5VzL/omurf/uKK/i5P6jLsm1LEEl4kNWWfb2i31q/Ak8DJKspU1eI0YFj9t+ X-Received: by 2002:a17:906:5bda:: with SMTP id w26mr42032263ejs.233.1606079412906; Sun, 22 Nov 2020 13:10:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606079412; cv=none; d=google.com; s=arc-20160816; b=rWMdM1Y7UsjqUOBe05RhBEoWgXc7Ot2/BA75lUp87RyBytc4/Wb8UU+fPgoO800LAt QcSofkyWaSyqNbYLQC7rzvphzf5ZufGxnYav4qo/EvKFMXzETsOapbMaNN7cA70RGw2h GgxtZ9WG8IBdt2ttZBKEmA4qiBh9fU5xESpRa+VRcpMajpDMAoKkS+6eyle8VWouykUg tLr2SYpwFFH5cY/FjdduVJvU1IflTela4EXKi+3IXBTWxQxu3tcOdfuemiqdFuw9HT1B MtuW8r3tif36mBqOXvRPJqrpDmPhT6dG7coR4JdwO9yEK8THzpfo3/IK4zB7GcB0EeEm J5Rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=oGrLrv8V+zVNACGxodYFf4G3ZA3jTIt+sbULpJuUy4c=; b=s525JJjNOCRqusbaCXmcDWz+bSvlW59XN9KlSGyzgqywG7hVrTHrFU1sta0mbB/NCJ 4rwIvwBcOypo3T7gvVRnBpxLdzAIcza1NfWLfNSPcIXOv3q3GmsEMoeP4UBUlCIAb5wm MlnJ6MFKELasHIM/JmNpoL1xNJWwzqoSRMuaQ1PUjaTtqkStZZ6g2cp+5qRpYxOa91BQ 7W4E6pKGrgQNCfTz9PQlbhrg5A7TncLfss57J4L9DwkkAnIiXc16YPCMinauioxwa8Hp S4ovRGrI2pBydW/PrNo76fLIHvR3bhxGlrs66ARRhRri5Po+u3/dTRAGvY3aiqnwyxjm gbuw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n15si5960053edy.106.2020.11.22.13.09.50; Sun, 22 Nov 2020 13:10:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727789AbgKVVAf (ORCPT + 99 others); Sun, 22 Nov 2020 16:00:35 -0500 Received: from jabberwock.ucw.cz ([46.255.230.98]:42558 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727418AbgKVVAf (ORCPT ); Sun, 22 Nov 2020 16:00:35 -0500 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 46B251C0BA9; Sun, 22 Nov 2020 22:00:32 +0100 (CET) Date: Sun, 22 Nov 2020 22:00:31 +0100 From: Pavel Machek To: Tushar Sugandhi Cc: zohar@linux.ibm.com, stephen.smalley.work@gmail.com, casey@schaufler-ca.com, agk@redhat.com, snitzer@redhat.com, gmazyland@gmail.com, paul@paul-moore.com, tyhicks@linux.microsoft.com, sashal@kernel.org, jmorris@namei.org, nramas@linux.microsoft.com, linux-integrity@vger.kernel.org, selinux@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, dm-devel@redhat.com Subject: Re: [PATCH v6 0/8] IMA: support for measuring kernel integrity critical data Message-ID: <20201122210031.GA26756@amd> References: <20201119232611.30114-1-tusharsu@linux.microsoft.com> <20201120124657.GA31468@duo.ucw.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >How is it supposed to be useful? > > > >I'm pretty sure there are critical data that are not measured by > >proposed module... and that are written under normal circumstances. > > > The goal of this series is to introduce the IMA hook > measure_critical_data() and the necessary policies to use it; and > illustrate that use with one example (SELinux). It is not scalable to > identify and update all the critical data sources to use the proposed > module at once. >=20 > A piecemeal approach to add more critical data measurement in subsequent > patches would be easy to implement and review. Basically every other data structure in kernel is "critical" by your definition, and you can't really measure them all; some of them change rather often. Going piecemeal does not really help here. Example of critical data structure: page table entries for process I own. Best regards, Pavel --=20 http://www.livejournal.com/~pavelmachek --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl+60W8ACgkQMOfwapXb+vIcigCeMzGk7j6mjC+lCez6JgfwCYJI Z1YAnihbhsor2KAe3Vx6iXF3suE279VG =O8SH -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--