From: Mimi Zohar <zohar@linux.ibm.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
dmitry.kasatkin@gmail.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com,
stephen.smalley.work@gmail.com, eparis@parisplace.org,
casey@schaufler-ca.com
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
bpf@vger.kernel.org, kpsingh@kernel.org, keescook@chromium.org,
nicolas.bouchinet@clip-os.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v10 0/4] evm: Do HMAC of multiple per LSM xattrs for new inodes
Date: Mon, 03 Apr 2023 06:36:33 -0400 [thread overview]
Message-ID: <3b6c773045d73ba1dcdb80dd9c6b7afcbd62cc42.camel@linux.ibm.com> (raw)
In-Reply-To: <20230331123221.3273328-1-roberto.sassu@huaweicloud.com>
On Fri, 2023-03-31 at 14:32 +0200, Roberto Sassu wrote:
> Changelog
>
> v9:
> - Ensure in reiserfs_security_write() that the full xattr name is not
> larger than XATTR_NAME_MAX
> - Rename num_filled_xattrs to xattr_count everywhere (suggested by Paul)
> - Rename lsm_find_xattr_slot() to lsm_get_xattr_slot() and add a proper
> documentation (suggested by Paul)
> - Return zero instead of -EOPNOTSUPP in evm_inode_init_security()
> (suggested by Paul)
> - Remove additional checks of new_xattrs array in
> security_inode_init_security() (suggested by Paul)
> - Handle the !initxattrs case similarly to the initxattrs case, except for
> not allocating the new_xattrs array in the former (suggested by Paul)
> - Remove local variable xattr in security_inode_init_security(), and use
> xattr_count instead for loop termination (suggested by Paul)
>
> v8:
> - Add a new reiserfs patch to write the full xattr name
> - Add num_filled_xattrs parameter to inode_init_security hook (suggested by
> Paul) and evm_inode_init_security()
> - Change default return value of inode_init_security hook to -EOPNOTSUPP
> - Rename lbs_xattr field of lsm_blob_sizes to lbs_xattr_count
> - Introduce lsm_find_xattr_slot() helper
> - Rename lsm_xattr parameter of evm_init_hmac() to xattrs
> - Retrieve the EVM xattr slot with lsm_find_xattr_slot() and double check
> with the xattr array terminator
> - Remove security_check_compact_filled_xattrs() (suggested by Paul)
Much better without security_check_compact_filled_xattrs(). Thank you!
> - Update security_inode_init_security() documentation
> - Ensure that inode_init_security hook incremented the number of filled
> slots if it returned zero
> - Ensure that xattr name and value are non-NULL in the filled slots
> - Add the xattr name assignment after the xattr value one (suggested by
> Paul)
> - Drop patches 1 - 3 (already in lsm/next)
>
--
thanks,
Mimi
prev parent reply other threads:[~2023-04-03 10:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 12:32 [PATCH v10 0/4] evm: Do HMAC of multiple per LSM xattrs for new inodes Roberto Sassu
2023-03-31 12:32 ` [PATCH v10 1/4] reiserfs: Add security prefix to xattr name in reiserfs_security_write() Roberto Sassu
2023-04-04 18:25 ` Paul Moore
2023-03-31 12:32 ` [PATCH v10 2/4] security: Allow all LSMs to provide xattrs for inode_init_security hook Roberto Sassu
2023-04-04 18:54 ` Paul Moore
2023-04-05 2:08 ` Casey Schaufler
2023-04-05 9:43 ` Roberto Sassu
2023-04-05 19:59 ` Paul Moore
2023-04-05 20:43 ` Casey Schaufler
2023-04-05 20:49 ` Paul Moore
2023-04-05 21:07 ` Casey Schaufler
2023-04-06 9:14 ` Roberto Sassu
2023-04-06 16:17 ` Casey Schaufler
2023-04-06 9:08 ` Roberto Sassu
2023-04-11 7:22 ` Mimi Zohar
2023-04-11 7:53 ` Roberto Sassu
2023-04-11 16:42 ` Casey Schaufler
2023-04-11 17:23 ` [PATCH] Smack modifications for: " Roberto Sassu
2023-04-11 17:54 ` Casey Schaufler
2023-04-12 7:22 ` Roberto Sassu
2023-04-12 20:29 ` Casey Schaufler
2023-04-13 7:11 ` Roberto Sassu
2023-04-17 16:41 ` Casey Schaufler
2023-04-18 7:05 ` Roberto Sassu
2023-04-18 16:02 ` Casey Schaufler
2023-04-19 13:46 ` Roberto Sassu
2023-04-19 19:25 ` Mengchi Cheng
2023-04-20 8:48 ` Roberto Sassu
2023-05-08 12:29 ` Roberto Sassu
2023-05-09 23:44 ` Mengchi Cheng
2023-05-09 23:56 ` Casey Schaufler
2023-04-19 21:00 ` Casey Schaufler
2023-04-20 8:50 ` Roberto Sassu
2023-04-20 10:44 ` Mimi Zohar
2023-04-20 14:10 ` Roberto Sassu
2023-04-11 17:25 ` [PATCH v10 2/4] " Roberto Sassu
2023-04-11 17:40 ` Casey Schaufler
2023-03-31 12:32 ` [PATCH v10 3/4] evm: Align evm_inode_init_security() definition with LSM infrastructure Roberto Sassu
2023-04-04 18:56 ` Paul Moore
2023-04-11 7:22 ` Mimi Zohar
2023-04-11 7:58 ` Roberto Sassu
2023-03-31 12:32 ` [PATCH v10 4/4] evm: Support multiple LSMs providing an xattr Roberto Sassu
2023-04-11 7:22 ` Mimi Zohar
2023-04-03 10:36 ` Mimi Zohar [this message]
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=3b6c773045d73ba1dcdb80dd9c6b7afcbd62cc42.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nicolas.bouchinet@clip-os.org \
--cc=paul@paul-moore.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.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).