From: Casey Schaufler <casey@schaufler-ca.com>
To: casey.schaufler@intel.com, jmorris@namei.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Cc: linux-audit@redhat.com, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
paul@paul-moore.com, stephen.smalley.work@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v34 00/29] LSM: Module stacking for AppArmor
Date: Fri, 15 Apr 2022 14:44:15 -0700 [thread overview]
Message-ID: <6558813d-e66e-688c-d664-68e00faf034e@schaufler-ca.com> (raw)
In-Reply-To: <20220415211801.12667-1-casey@schaufler-ca.com>
On 4/15/2022 2:17 PM, Casey Schaufler wrote:
> This patchset provides the changes required for
> the AppArmor security module to stack safely with any other.
Apologies for the inadvertent resend of this version.
V35 coming soon.
next prev parent reply other threads:[~2022-04-15 21:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220415211801.12667-1-casey.ref@schaufler-ca.com>
2022-04-15 21:17 ` Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 01/29] integrity: disassociate ima_filter_rule from security_audit_rule Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 02/29] LSM: Infrastructure management of the sock security Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 03/29] LSM: Add the lsmblob data structure Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 04/29] LSM: provide lsm name and id slot mappings Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 05/29] IMA: avoid label collisions with stacked LSMs Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 06/29] LSM: Use lsmblob in security_audit_rule_match Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 07/29] LSM: Use lsmblob in security_kernel_act_as Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 08/29] LSM: Use lsmblob in security_secctx_to_secid Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 09/29] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 10/29] LSM: Use lsmblob in security_ipc_getsecid Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 11/29] LSM: Use lsmblob in security_current_getsecid Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 12/29] LSM: Use lsmblob in security_inode_getsecid Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 13/29] LSM: Use lsmblob in security_cred_getsecid Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 14/29] LSM: Specify which LSM to display Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 15/29] LSM: Ensure the correct LSM context releaser Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 16/29] LSM: Use lsmcontext in security_secid_to_secctx Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 17/29] LSM: Use lsmcontext in security_inode_getsecctx Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 18/29] LSM: security_secid_to_secctx in netlink netfilter Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 19/29] NET: Store LSM netlabel data in a lsmblob Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 20/29] binder: Pass LSM identifier for confirmation Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 21/29] LSM: Extend security_secid_to_secctx to include module selection Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 22/29] Audit: Keep multiple LSM data in audit_names Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 23/29] Audit: Create audit_stamp structure Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 24/29] LSM: Add a function to report multiple LSMs Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 25/29] Audit: Allow multiple records in an audit_buffer Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 26/29] Audit: Add record for multiple task security contexts Casey Schaufler
2022-04-15 21:17 ` [PATCH v34 27/29] Audit: Add record for multiple object contexts Casey Schaufler
2022-04-15 21:18 ` [PATCH v34 28/29] LSM: Add /proc attr entry for full LSM context Casey Schaufler
2022-04-15 21:18 ` [PATCH v34 29/29] AppArmor: Remove the exclusive flag Casey Schaufler
2022-04-15 21:44 ` Casey Schaufler [this message]
[not found] <20220407212230.12893-1-casey.ref@schaufler-ca.com>
2022-04-07 21:22 ` [PATCH v34 00/29] LSM: Module stacking for AppArmor Casey Schaufler
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=6558813d-e66e-688c-d664-68e00faf034e@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=casey.schaufler@intel.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=selinux@vger.kernel.org \
--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
all inboxes | Powered by JetHome®