Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp4621694iob; Sun, 8 May 2022 19:32:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxMphfcZ3v8ytZ6Fj8mzOeTQVjqE+vQhLzppWI5grpE5VR8zPbHf0O+pqisjn2JUpJGGqBM X-Received: by 2002:a05:6a00:1707:b0:50e:23d:834f with SMTP id h7-20020a056a00170700b0050e023d834fmr13960920pfc.82.1652063565686; Sun, 08 May 2022 19:32:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652063565; cv=none; d=google.com; s=arc-20160816; b=Isy9/Lu16LaJhku5gLmL4Wjt4gt0xv1jjt2Kib49XaEqpuxRA5t65mfgmwIddFKqMI O06kIvcRxisxp88L6+N2JVuu2fTsCTjmulVLI8I6SP0jcJ5/RlvIeZ7HcwC4z0oL1DQf GMtLP4jfQ6Ep5pD7pbpBP4lfnOOxwLJyJhwXaUVo4LmeocERSpmelfHxvKJs3pqz0Kyg 0hGtmQMQNpLKGqHgEsYJMMdAeZUf5BX30aqm77WVZJ8AILCIy4lp8l2lKIc3pjBdnlC5 0Ukm2yX+S1/2Xi/63Tr0dzOzyTKrstxPymo6XRQtxmnm5m6wAHU19VhsxagByvhwLh9p jyLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=9VCCMYA2saXgFhGUsRzgpbtwBPHpjOWbNPgHdeeLmZ8=; b=UlOxrS0eYmAYMUXp5XNpfA4U8CUjlNsBWhKxA+1MiCdniM/e5vcXKa0ZtE/v9rwCVX R1VY1IlmzGNmbAVfJOM5+8BBwfRDJI4HACM0zQ8wSp57fUbPQAx2nZNvKvOcXbzWxfCv 36qEXv9QaCryrGnbjKPu1P1D8GpSP8xyo8gTBJphq4QfeZJCoWirTPwshHfzylT6BZut Ua+uU2tKk1VgqQBbLXKY8MF8sRVT456mtq+7EfoP0VLDTejJPjvSDbuY62rvRB3THPEd UFKJcwnvo6By49VC1+LFcCGE4+RlbalUziEQMcUzbR1Za+EdWyOdE1SBybWWcO1oPpMH p7VQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=ko4l5bBv; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id t190-20020a6381c7000000b003c5d888f2e5si12611916pgd.364.2022.05.08.19.32.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 May 2022 19:32:45 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=ko4l5bBv; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 41B5972E2D; Sun, 8 May 2022 19:31:35 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377171AbiEEMgX (ORCPT + 99 others); Thu, 5 May 2022 08:36:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39072 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1376940AbiEEMfv (ORCPT ); Thu, 5 May 2022 08:35:51 -0400 Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E30D455360; Thu, 5 May 2022 05:32:10 -0700 (PDT) Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 245BiioQ014442; Thu, 5 May 2022 12:32:08 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding; s=pp1; bh=9VCCMYA2saXgFhGUsRzgpbtwBPHpjOWbNPgHdeeLmZ8=; b=ko4l5bBvi2t7TFjJqU0dmjCg0sYM/c0rgcjPJzoam0Gamig0kpCLdRESV4atRFx9cBMT t99roaFJj/o06QOIfo1XYEyddZK++4zU3t7Xe5N3Ey1pnqGrFjfFv/RHQJGuc0Z7XUT5 66NXfny/tu9m4jInNmkmtX5BsesdGrPVb0Y6/PJBOVCWeZQPqlITBd28ZYFcfaipW7ZA AxxLuFvmitryYHJkxD7nQEAJAXBwoP1swJ+UQXcUpRSnwpDYTquVM9IRYmNubzkGJDk3 43/B18OcndCYn7GvDBNpF8xdvHslqLIoNeBLP10+TQ/zW9s2L+8wHBc73wGzUSMp8kq9 Cw== Received: from ppma06ams.nl.ibm.com (66.31.33a9.ip4.static.sl-reverse.com [169.51.49.102]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3fvdys8waf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 05 May 2022 12:32:08 +0000 Received: from pps.filterd (ppma06ams.nl.ibm.com [127.0.0.1]) by ppma06ams.nl.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 245CSSgi023596; Thu, 5 May 2022 12:32:06 GMT Received: from b06cxnps3075.portsmouth.uk.ibm.com (d06relay10.portsmouth.uk.ibm.com [9.149.109.195]) by ppma06ams.nl.ibm.com with ESMTP id 3frvcj772d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 05 May 2022 12:32:05 +0000 Received: from d06av22.portsmouth.uk.ibm.com (d06av22.portsmouth.uk.ibm.com [9.149.105.58]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 245CW2al50594096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 5 May 2022 12:32:02 GMT Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 88DE34C046; Thu, 5 May 2022 12:32:02 +0000 (GMT) Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8354B4C040; Thu, 5 May 2022 12:32:01 +0000 (GMT) Received: from li-f45666cc-3089-11b2-a85c-c57d1a57929f.ibm.com.com (unknown [9.65.81.94]) by d06av22.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 5 May 2022 12:32:01 +0000 (GMT) From: Mimi Zohar To: linux-integrity@vger.kernel.org Cc: Mimi Zohar , Eric Biggers , Stefan Berger , linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v9 7/7] fsverity: update the documentation Date: Thu, 5 May 2022 08:31:41 -0400 Message-Id: <20220505123141.1599622-8-zohar@linux.ibm.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20220505123141.1599622-1-zohar@linux.ibm.com> References: <20220505123141.1599622-1-zohar@linux.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: VlAR-KLR5hwIRpCLmgp2ea4gy9gfDvij X-Proofpoint-ORIG-GUID: VlAR-KLR5hwIRpCLmgp2ea4gy9gfDvij X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.858,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-05-05_05,2022-05-05_01,2022-02-23_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 impostorscore=0 priorityscore=1501 lowpriorityscore=0 adultscore=0 clxscore=1015 mlxscore=0 suspectscore=0 phishscore=0 spamscore=0 bulkscore=0 mlxlogscore=802 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2205050091 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Update the fsverity documentation related to IMA signature support. Acked-by: Stefan Berger Signed-off-by: Mimi Zohar --- Documentation/filesystems/fsverity.rst | 35 +++++++++++++++++--------- 1 file changed, 23 insertions(+), 12 deletions(-) diff --git a/Documentation/filesystems/fsverity.rst b/Documentation/filesystems/fsverity.rst index 8cc536d08f51..b7d42fd65e9d 100644 --- a/Documentation/filesystems/fsverity.rst +++ b/Documentation/filesystems/fsverity.rst @@ -70,12 +70,23 @@ must live on a read-write filesystem because they are independently updated and potentially user-installed, so dm-verity cannot be used. The base fs-verity feature is a hashing mechanism only; actually -authenticating the files is up to userspace. However, to meet some -users' needs, fs-verity optionally supports a simple signature -verification mechanism where users can configure the kernel to require -that all fs-verity files be signed by a key loaded into a keyring; see -`Built-in signature verification`_. Support for fs-verity file hashes -in IMA (Integrity Measurement Architecture) policies is also planned. +authenticating the files may be done by: + +* Userspace-only + +* Builtin signature verification + userspace policy + + fs-verity optionally supports a simple signature verification + mechanism where users can configure the kernel to require that + all fs-verity files be signed by a key loaded into a keyring; + see `Built-in signature verification`_. + +* Integrity Measurement Architecture (IMA) + + IMA supports including fs-verity file digests and signatures in the + IMA measurement list and verifying fs-verity based file signatures + stored as security.ima xattrs, based on policy. + User API ======== @@ -653,12 +664,12 @@ weren't already directly answered in other parts of this document. hashed and what to do with those hashes, such as log them, authenticate them, or add them to a measurement list. - IMA is planned to support the fs-verity hashing mechanism as an - alternative to doing full file hashes, for people who want the - performance and security benefits of the Merkle tree based hash. - But it doesn't make sense to force all uses of fs-verity to be - through IMA. As a standalone filesystem feature, fs-verity - already meets many users' needs, and it's testable like other + IMA supports the fs-verity hashing mechanism as an alternative + to full file hashes, for those who want the performance and + security benefits of the Merkle tree based hash. However, it + doesn't make sense to force all uses of fs-verity to be through + IMA. fs-verity already meets many users' needs even as a + standalone filesystem feature, and it's testable like other filesystem features e.g. with xfstests. :Q: Isn't fs-verity useless because the attacker can just modify the -- 2.27.0