From: Mimi Zohar <zohar@linux.ibm.com>
To: Oleksandr Tymoshenko <ovt@google.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Nayna Jain <nayna@linux.ibm.com>
Cc: rnv@google.com, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
Date: Wed, 27 Sep 2023 06:44:23 -0400 [thread overview]
Message-ID: <0d71b67e129b095ea698b39d0b1d05119bd0b464.camel@linux.ibm.com> (raw)
In-Reply-To: <CACGj0Cgh7Vjf5EcY7F+pf9bCjXhhJYN-xf3NeC8WWjT4+j9RrA@mail.gmail.com>
On Mon, 2023-09-25 at 21:20 -0700, Oleksandr Tymoshenko wrote:
> On Wed, Sep 20, 2023 at 11:45 PM Oleksandr Tymoshenko <ovt@google.com> wrote:
> >
> > The removal of IMA_TRUSTED_KEYRING made IMA_LOAD_X509
> > and IMA_BLACKLIST_KEYRING unavailable because the latter
> > two depend on the former. Since IMA_TRUSTED_KEYRING was
> > deprecated in favor of INTEGRITY_TRUSTED_KEYRING use it
> > as a dependency for the two Kconfigs affected by the
> > deprecation.
> >
> > Fixes: 5087fd9e80e5 ("ima: Remove deprecated IMA_TRUSTED_KEYRING Kconfig")
> > Signed-off-by: Oleksandr Tymoshenko <ovt@google.com>
>
> Gentle ping, IMA_LOAD_X509 and IMA_BLACKLIST_KEYRING options are
> currently broken on all branches.
Sorry for the delay. It's now in linux-next.
--
thanks,
Mimi
next prev parent reply other threads:[~2023-09-27 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 6:45 [PATCH] ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig Oleksandr Tymoshenko
2023-09-26 4:20 ` Oleksandr Tymoshenko
2023-09-27 10:44 ` Mimi Zohar [this message]
2023-09-26 21:32 ` Nayna
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=0d71b67e129b095ea698b39d0b1d05119bd0b464.camel@linux.ibm.com \
--to=zohar@linux.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=nayna@linux.ibm.com \
--cc=ovt@google.com \
--cc=paul@paul-moore.com \
--cc=rnv@google.com \
--cc=serge@hallyn.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).