Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1235800pxb; Fri, 20 Nov 2020 04:50:13 -0800 (PST) X-Google-Smtp-Source: ABdhPJzuwzFc7ilP9BV+eFEXpIccpuRJVKu7C70tc2imbmHFFgBPSmqqmg60G0nuop8+HtGn5WDQ X-Received: by 2002:a17:906:5a8b:: with SMTP id l11mr25353045ejq.99.1605876613429; Fri, 20 Nov 2020 04:50:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605876613; cv=none; d=google.com; s=arc-20160816; b=lBT0lYc77RPRbajzKkbBMXpPgaNMHLE0WjQuNEwI0cqfdte4AhYmJV21Z+TepTUO3S ZmYg64ox9xWA3ITMOOwoGjxe6mLYPIq2wL9xdLeW1QloFSm8ctbi+OHzILRbf6Sw3xZ+ Rr+xwWvxnJWigNYcs8BkH2pv4ohpY5DDKWVhOAelKVviMSselp1oNrqrnmeteRDf0/RA jNK4Yi/dU33zAtHIf/yQ1WEBwJ26B4AmtD5LhgRrMk0uKn4R9KAt95cQJtj4JT7K7dKo KYeP5NgYZbYyU7LZPtpecWstiA97TztzjpUuulU2m/y9aD9TyY5rzk9z7+HByUhNjLA2 +bmQ== 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=z1KkbLf5ywCEJtJNuPeo+1wrbpOzbgZ8vSrRA+UNAms=; b=D5Ohb7G9aX5Y9onsounp5XJl7UcL6F3WE7G81HO4cZkOFTPotURaJwncp95nGuhxqt e4M0h4sv6mLYAqea+AgCn4MbURanBVsxsJoLEX4x+2l8sH7FpAQ2Tj18trIvr2kow76C 3aQ+UF+cpNR4+n97sntKFHZHaHaUMhF3hzn88ufim3WEatdYvqvDAGR8rMmz0gK4n4Ck o5Mfp9BmHdb9G0UST2MH79aSV8jG9PACAENNh2T/FYEsrREreduVWPbFt2p41h+CciWP qiMuvBsS+Jun6MhoCw5acrrV8sZ4+KNaJNc49uTmCIdyU/2YxmSjST9vKOxgeDUvovzX YUuw== 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 y3si1570172edq.324.2020.11.20.04.49.50; Fri, 20 Nov 2020 04:50:13 -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 S1728093AbgKTMrB (ORCPT + 99 others); Fri, 20 Nov 2020 07:47:01 -0500 Received: from jabberwock.ucw.cz ([46.255.230.98]:36618 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727789AbgKTMrB (ORCPT ); Fri, 20 Nov 2020 07:47:01 -0500 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id ECF241C0BBF; Fri, 20 Nov 2020 13:46:57 +0100 (CET) Date: Fri, 20 Nov 2020 13:46:57 +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: <20201120124657.GA31468@duo.ucw.cz> References: <20201119232611.30114-1-tusharsu@linux.microsoft.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <20201119232611.30114-1-tusharsu@linux.microsoft.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu 2020-11-19 15:26:03, Tushar Sugandhi wrote: > Kernel integrity critical data can be defined as the in-memory kernel > data which if accidentally or maliciously altered, can compromise the > integrity of the system. Is that an useful definition? > There are several kernel subsystems that contain integrity critical > data - e.g. LSMs like SELinux, or AppArmor; or device-mapper targets > like dm-crypt, dm-verity etc. Examples of critical data could be kernel > in-memory r/o structures, hash of the memory structures, or data that > represents a linux kernel subsystem state. >=20 > This patch set defines a new IMA hook namely ima_measure_critical_data() > to measure the critical data. Kernel subsystems can use this > functionality, to take advantage of IMA's measuring and quoting=20 > abilities - thus ultimately enabling remote attestation for the > subsystem specific information stored in the kernel memory. 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. Best regards, Pavel --=20 http://www.livejournal.com/~pavelmachek --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCX7e6wQAKCRAw5/Bqldv6 8i6vAKC6FrLMFyZX0lHzJkX+8Mez8H3kogCeJ64mXaqCarNAouB4RShXr1Nthec= =jlIk -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--