From: Roberto Sassu <roberto.sassu@huawei.com>
To: "zohar@linux.ibm.com" <zohar@linux.ibm.com>,
"mjg59@srcf.ucam.org" <mjg59@srcf.ucam.org>
Cc: "linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RESEND][PATCH 05/12] evm: Introduce evm_hmac_disabled() to safely ignore verification errors
Date: Thu, 20 May 2021 08:51:07 +0000 [thread overview]
Message-ID: <6d7e059876b64f249b9a01d8b7696e29@huawei.com> (raw)
In-Reply-To: <20210520084831.465058-1-roberto.sassu@huawei.com>
> From: Roberto Sassu
> Sent: Thursday, May 20, 2021 10:49 AM
> When a file is being created, LSMs can set the initial label with the
> inode_init_security hook. If no HMAC key is loaded, the new file will have
> LSM xattrs but not the HMAC. It is also possible that the file remains
> without protected xattrs after creation if no active LSM provided it, or
> because the filesystem does not support them.
>
> Unfortunately, EVM will deny any further metadata operation on new files,
> as evm_protect_xattr() will return the INTEGRITY_NOLABEL error if protected
> xattrs exist without security.evm, INTEGRITY_NOXATTRS if no protected
> xattrs exist or INTEGRITY_UNKNOWN if xattrs are not supported. This would
> limit the usability of EVM when only a public key is loaded, as commands
> such as cp or tar with the option to preserve xattrs won't work.
>
> This patch introduces the evm_hmac_disabled() function to determine whether
> or not it is safe to ignore verification errors, based on the ability of
> EVM to calculate HMACs. If the HMAC key is not loaded, and it cannot be
> loaded in the future due to the EVM_SETUP_COMPLETE initialization flag,
> allowing an operation despite the attrs/xattrs being found invalid will not
> make them valid.
>
> Since the post hooks can be executed even when the HMAC key is not loaded,
> this patch also ensures that the EVM_INIT_HMAC initialization flag is set
> before the post hooks call evm_update_evmxattr().
Resending, to ignore INTEGRITY_UNKNOWN when a filesystem does not
support xattrs.
Roberto
HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
Managing Director: Li Peng, Li Jian, Shi Yanli
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> Suggested-by: Mimi Zohar <zohar@linux.ibm.com>
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
> security/integrity/evm/evm_main.c | 39 ++++++++++++++++++++++++++++++-
> 1 file changed, 38 insertions(+), 1 deletion(-)
>
> diff --git a/security/integrity/evm/evm_main.c
> b/security/integrity/evm/evm_main.c
> index 782915117175..4206c7e492ae 100644
> --- a/security/integrity/evm/evm_main.c
> +++ b/security/integrity/evm/evm_main.c
> @@ -90,6 +90,24 @@ static bool evm_key_loaded(void)
> return (bool)(evm_initialized & EVM_KEY_MASK);
> }
>
> +/*
> + * This function determines whether or not it is safe to ignore verification
> + * errors, based on the ability of EVM to calculate HMACs. If the HMAC key
> + * is not loaded, and it cannot be loaded in the future due to the
> + * EVM_SETUP_COMPLETE initialization flag, allowing an operation despite
> the
> + * attrs/xattrs being found invalid will not make them valid.
> + */
> +static bool evm_hmac_disabled(void)
> +{
> + if (evm_initialized & EVM_INIT_HMAC)
> + return false;
> +
> + if (!(evm_initialized & EVM_SETUP_COMPLETE))
> + return false;
> +
> + return true;
> +}
> +
> static int evm_find_protected_xattrs(struct dentry *dentry)
> {
> struct inode *inode = d_backing_inode(dentry);
> @@ -338,6 +356,10 @@ static int evm_protect_xattr(struct dentry *dentry,
> const char *xattr_name,
> if (evm_status == INTEGRITY_NOXATTRS) {
> struct integrity_iint_cache *iint;
>
> + /* Exception if the HMAC is not going to be calculated. */
> + if (evm_hmac_disabled())
> + return 0;
> +
> iint = integrity_iint_find(d_backing_inode(dentry));
> if (iint && (iint->flags & IMA_NEW_FILE))
> return 0;
> @@ -354,6 +376,10 @@ static int evm_protect_xattr(struct dentry *dentry,
> const char *xattr_name,
> -EPERM, 0);
> }
> out:
> + /* Exception if the HMAC is not going to be calculated. */
> + if (evm_hmac_disabled() && (evm_status == INTEGRITY_NOLABEL ||
> + evm_status == INTEGRITY_UNKNOWN))
> + return 0;
> if (evm_status != INTEGRITY_PASS)
> integrity_audit_msg(AUDIT_INTEGRITY_METADATA,
> d_backing_inode(dentry),
> dentry->d_name.name,
> "appraise_metadata",
> @@ -474,6 +500,9 @@ void evm_inode_post_setxattr(struct dentry *dentry,
> const char *xattr_name,
> if (!strcmp(xattr_name, XATTR_NAME_EVM))
> return;
>
> + if (!(evm_initialized & EVM_INIT_HMAC))
> + return;
> +
> evm_update_evmxattr(dentry, xattr_name, xattr_value,
> xattr_value_len);
> }
>
> @@ -497,6 +526,9 @@ void evm_inode_post_removexattr(struct dentry
> *dentry, const char *xattr_name)
> if (!strcmp(xattr_name, XATTR_NAME_EVM))
> return;
>
> + if (!(evm_initialized & EVM_INIT_HMAC))
> + return;
> +
> evm_update_evmxattr(dentry, xattr_name, NULL, 0);
> }
>
> @@ -522,7 +554,9 @@ int evm_inode_setattr(struct dentry *dentry, struct
> iattr *attr)
> return 0;
> evm_status = evm_verify_current_integrity(dentry);
> if ((evm_status == INTEGRITY_PASS) ||
> - (evm_status == INTEGRITY_NOXATTRS))
> + (evm_status == INTEGRITY_NOXATTRS) ||
> + (evm_hmac_disabled() && (evm_status == INTEGRITY_NOLABEL ||
> + evm_status == INTEGRITY_UNKNOWN)))
> return 0;
> integrity_audit_msg(AUDIT_INTEGRITY_METADATA,
> d_backing_inode(dentry),
> dentry->d_name.name, "appraise_metadata",
> @@ -548,6 +582,9 @@ void evm_inode_post_setattr(struct dentry *dentry,
> int ia_valid)
>
> evm_reset_status(dentry->d_inode);
>
> + if (!(evm_initialized & EVM_INIT_HMAC))
> + return;
> +
> if (ia_valid & (ATTR_MODE | ATTR_UID | ATTR_GID))
> evm_update_evmxattr(dentry, NULL, NULL, 0);
> }
> --
> 2.25.1
next prev parent reply other threads:[~2021-05-20 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 15:27 [PATCH v7 00/12] evm: Improve usability of portable signatures Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 01/12] evm: Execute evm_inode_init_security() only when an HMAC key is loaded Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 02/12] evm: Load EVM key in ima_load_x509() to avoid appraisal Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 03/12] evm: Refuse EVM_ALLOW_METADATA_WRITES only if an HMAC key is loaded Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 04/12] evm: Introduce evm_revalidate_status() Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 05/12] evm: Introduce evm_hmac_disabled() to safely ignore verification errors Roberto Sassu
2021-05-20 8:48 ` [RESEND][PATCH " Roberto Sassu
2021-05-20 8:51 ` Roberto Sassu [this message]
2021-05-14 15:27 ` [PATCH v7 06/12] evm: Allow xattr/attr operations for portable signatures Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 07/12] evm: Pass user namespace to set/remove xattr hooks Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 08/12] evm: Allow setxattr() and setattr() for unmodified metadata Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 09/12] evm: Deprecate EVM_ALLOW_METADATA_WRITES Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 10/12] ima: Allow imasig requirement to be satisfied by EVM portable signatures Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 11/12] ima: Introduce template field evmsig and write to field sig as fallback Roberto Sassu
2021-05-14 15:27 ` [PATCH v7 12/12] ima: Don't remove security.ima if file must not be appraised Roberto Sassu
2021-05-20 18:55 ` [PATCH v7 00/12] evm: Improve usability of portable signatures Mimi Zohar
2021-05-21 7:07 ` Roberto Sassu
2021-05-21 17:31 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d7e059876b64f249b9a01d8b7696e29@huawei.com \
--to=roberto.sassu@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).