LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> To: "Serge E. Hallyn" <serge@hallyn.com> Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>, Mimi Zohar <zohar@linux.vnet.ibm.com>, Dmitry Kasatkin <dmitry.kasatkin@gmail.com> Subject: Re: [PATCH 3/4] ima: Improvements in ima_appraise_measurement() Date: Wed, 14 Mar 2018 21:03:36 -0300 [thread overview] Message-ID: <87efkmjjc7.fsf@morokweng.localdomain> (raw) In-Reply-To: <20180314214045.GC14289@mail.hallyn.com> Hello Serge, Thanks for quickly reviewing these patches! Serge E. Hallyn <serge@hallyn.com> writes: > Quoting Thiago Jung Bauermann (bauerman@linux.vnet.ibm.com): >> From: Mimi Zohar <zohar@linux.vnet.ibm.com> >> @@ -241,16 +241,20 @@ int ima_appraise_measurement(enum ima_hooks func, >> } >> >> status = evm_verifyxattr(dentry, XATTR_NAME_IMA, xattr_value, rc, iint); >> - if ((status != INTEGRITY_PASS) && >> - (status != INTEGRITY_PASS_IMMUTABLE) && >> - (status != INTEGRITY_UNKNOWN)) { >> - if ((status == INTEGRITY_NOLABEL) >> - || (status == INTEGRITY_NOXATTRS)) >> - cause = "missing-HMAC"; >> - else if (status == INTEGRITY_FAIL) >> - cause = "invalid-HMAC"; >> + switch (status) { >> + case INTEGRITY_PASS: >> + case INTEGRITY_PASS_IMMUTABLE: >> + case INTEGRITY_UNKNOWN: > > Wouldn't it be more future-proof to replace this with a 'default', or > to at least add a "default: BUG()" to catch new status values? I agree. I like the "default: BUG()" option. >> + break; >> + case INTEGRITY_NOXATTRS: /* No EVM protected xattrs. */ >> + case INTEGRITY_NOLABEL: /* No security.evm xattr. */ >> + cause = "missing-HMAC"; >> + goto out; >> + case INTEGRITY_FAIL: /* Invalid HMAC/signature. */ >> + cause = "invalid-HMAC"; >> goto out; >> } >> + >> switch (xattr_value->type) { >> case IMA_XATTR_DIGEST_NG: >> /* first byte contains algorithm id */ >> @@ -316,17 +320,20 @@ int ima_appraise_measurement(enum ima_hooks func, >> integrity_audit_msg(AUDIT_INTEGRITY_DATA, inode, filename, >> op, cause, rc, 0); >> } else if (status != INTEGRITY_PASS) { >> + /* Fix mode, but don't replace file signatures. */ >> if ((ima_appraise & IMA_APPRAISE_FIX) && >> (!xattr_value || >> xattr_value->type != EVM_IMA_XATTR_DIGSIG)) { >> if (!ima_fix_xattr(dentry, iint)) >> status = INTEGRITY_PASS; >> - } else if ((inode->i_size == 0) && >> - (iint->flags & IMA_NEW_FILE) && >> - (xattr_value && >> - xattr_value->type == EVM_IMA_XATTR_DIGSIG)) { >> + } >> + >> + /* Permit new files with file signatures, but without data. */ >> + if (inode->i_size == 0 && iint->flags & IMA_NEW_FILE && > > This may be correct, but it's not identical to what you're replacing. > Since in either case you're setting status to INTEGRITY_PASS the final > result is the same, but with a few extra possible steps. Not sure > whether that matters. Good point. I'll have to defer this one to Mimi though. > >> + xattr_value && xattr_value->type == EVM_IMA_XATTR_DIGSIG) { >> status = INTEGRITY_PASS; >> } >> + >> integrity_audit_msg(AUDIT_INTEGRITY_DATA, inode, filename, >> op, cause, rc, 0); >> } else { -- Thiago Jung Bauermann IBM Linux Technology Center
next prev parent reply other threads:[~2018-03-15 0:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-14 20:20 [PATCH 0/4] Code improvements in integrity and IMA Thiago Jung Bauermann 2018-03-14 20:20 ` [PATCH 1/4] integrity: Remove unused macro IMA_ACTION_RULE_FLAGS Thiago Jung Bauermann 2018-03-14 21:33 ` Serge E. Hallyn 2018-03-14 20:20 ` [PATCH 2/4] ima: Simplify ima_eventsig_init() Thiago Jung Bauermann 2018-03-14 21:31 ` Serge E. Hallyn 2018-03-14 20:20 ` [PATCH 3/4] ima: Improvements in ima_appraise_measurement() Thiago Jung Bauermann 2018-03-14 21:40 ` Serge E. Hallyn 2018-03-15 0:03 ` Thiago Jung Bauermann [this message] 2018-03-15 19:18 ` Mimi Zohar 2018-03-15 20:33 ` Thiago Jung Bauermann 2018-03-17 15:09 ` Serge E. Hallyn 2018-03-14 20:20 ` [PATCH 4/4] integrity: Introduce struct evm_xattr Thiago Jung Bauermann 2018-03-15 21:01 ` [PATCH 0/4] Code improvements in integrity and IMA 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=87efkmjjc7.fsf@morokweng.localdomain \ --to=bauerman@linux.vnet.ibm.com \ --cc=dmitry.kasatkin@gmail.com \ --cc=jmorris@namei.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=serge@hallyn.com \ --cc=zohar@linux.vnet.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: linkBe 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).