All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Gallop Permission <permissiontogallop@gmail.com>
Cc: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] KEYS: request_key: enforce keyring restrictions on constructed keys
Date: Sat, 31 Oct 2026 09:58:47 +0200	[thread overview]
Message-ID: <auWft1EcujMbVy8S@kernel.org> (raw)
In-Reply-To: <auWfECT7SNhBDZtl@kernel.org>

On Sat, Oct 31, 2026 at 09:56:03AM +0200, Jarkko Sakkinen wrote:
> On Sat, Oct 31, 2026 at 09:53:54AM +0200, Jarkko Sakkinen wrote:
> > On Sat, Oct 31, 2026 at 10:10:36AM +0530, Gallop Permission wrote:
> > > Hi, Jarkko
> > > 
> > > 1. you asked: What does "key becoming positive" mean here broken down?
> > >     Here key becoming positive” means the transition from
> > > KEY_IS_UNINSTANTIATED to KEY_IS_POSITIVE
> > >     after the type’s instantiate() succeeded and the payload is present.
> > 
> > Great use concrete termininology.
> 
> Please also read:
> 
> https://docs.kernel.org/process/email-clients.html
> 
> Especially quoting part. Your responses are somewhat difficult to read
> and we don't prefer top-posting.

One more thing: the short summary (subject) is incorrect as we already
do enforce restrictions.

I missed this one earlier. Just put something more appropriate, that's
all.

Br, Jarkko

  reply	other threads:[~2026-10-31  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 17:39 [PATCH] KEYS: request_key: enforce keyring restrictions on constructed keys Anvik Loitongbam
2026-10-30 18:07 ` sashiko-bot
2026-10-30 18:18 ` Jarkko Sakkinen
2026-10-31  4:40   ` Gallop Permission
2026-10-31  7:53     ` Jarkko Sakkinen
2026-10-31  7:56       ` Jarkko Sakkinen
2026-10-31  7:58         ` Jarkko Sakkinen [this message]
2026-10-31  8:20 ` Jarkko Sakkinen
2026-10-31  9:19   ` Jarkko Sakkinen

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=auWft1EcujMbVy8S@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=permissiontogallop@gmail.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.