From: Greg KH <gregkh@linuxfoundation.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "KEYS: prevent keys from being removed from specified keyrings" has been added to the 3.10-stable tree
Date: Wed, 20 Jan 2016 10:36:33 -0800 [thread overview]
Message-ID: <20160120183633.GA527@kroah.com> (raw)
In-Reply-To: <1453313747.4396.5.camel@linux.vnet.ibm.com>
On Wed, Jan 20, 2016 at 01:15:47PM -0500, Mimi Zohar wrote:
> Hi Greg,
>
> The concept of not being able to remove a key from a keyring was
> introduced to prevent keys from being removed from the blacklist
> keyring. The blacklist keyring was just upstreamed in the current open
> window. I don't see a need to backport either this patch or the "KEYS:
> refcount bug fix" patch.
Ah, ok, remove this for all stable kernel trees, right? For some reason
I thought this was resolving a different key security "issue" that was
recently reported...
thanks,
greg k-h
next prev parent reply other threads:[~2016-01-20 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 16:58 Patch "KEYS: prevent keys from being removed from specified keyrings" has been added to the 3.10-stable tree gregkh
2016-01-20 18:15 ` Mimi Zohar
2016-01-20 18:36 ` Greg KH [this message]
2016-01-20 19:23 ` 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=20160120183633.GA527@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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: 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).