From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>,
Steve French <sfrench@samba.org>,
Chuck Lever <chuck.lever@oracle.com>
Cc: Paulo Alcantara <pc@manguebit.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jeffrey Altman <jaltman@auristor.com>,
hch@infradead.org, linux-afs@lists.infradead.org,
linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Keyrings: How to make them more useful
Date: Mon, 16 Jun 2025 16:30:05 -0400 [thread overview]
Message-ID: <0e70574bfae43ce939d67e89c858f303ae7ac204.camel@linux.ibm.com> (raw)
In-Reply-To: <462886.1749731810@warthog.procyon.org.uk>
On Thu, 2025-06-12 at 13:36 +0100, David Howells wrote:
[ ...]
> (4) I think the keyring ACLs idea need to be revived. We have a whole bunch
> of different keyrings, each with a specific 'domain' of usage for the
> keys contained therein for checking signatures on things. Can we reduce
> this to one keyring and use ACLs to declare the specific purposes for
> which a key may be used or the specific tasks that may use it? Use
> special subject IDs (ie. not simply UIDs/GIDs) to mark this.
David, which keyrings are you referring to? What do you mean by 'domain' of
usage? At what level of granularity are you thinking of? This needs to be
describe in more detail.
thanks,
Mimi
next prev parent reply other threads:[~2025-06-16 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 12:36 [RFC] Keyrings: How to make them more useful David Howells
2025-06-12 14:10 ` Benjamin Coddington
2025-06-12 18:27 ` James Bottomley
2025-06-12 20:36 ` David Howells
2025-06-13 15:40 ` James Bottomley
2025-06-16 20:30 ` Mimi Zohar [this message]
2025-06-17 13:54 ` 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=0e70574bfae43ce939d67e89c858f303ae7ac204.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jaltman@auristor.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=sfrench@samba.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 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).