From: David Howells <dhowells@redhat.com>
To: Arun Raghavan <arunsr@cse.iitk.ac.in>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow clients to set key perms in key_create_or_update()
Date: Fri, 07 Mar 2008 09:48:38 +0000 [thread overview]
Message-ID: <25831.1204883318@redhat.com> (raw)
In-Reply-To: <47CFD7F8.9010903@cse.iitk.ac.in>
Arun Raghavan <arunsr@cse.iitk.ac.in> wrote:
> The key_create_or_update() function provided by the keyring code has a default
> set of permissions that are always applied to the key when created. This might
> not be desirable to all clients.
>
> Here's a patch that adds a "perm" parameter to the function to address this,
> which can be set to KEY_PERM_UNDEF to revert to the current behaviour.
I'll get to this shortly. I'm just creating another keyrings patch, so I'll
look at yours afterwards.
David
next prev parent reply other threads:[~2008-03-07 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 11:39 [PATCH] Allow clients to set key perms in key_create_or_update() Arun Raghavan
2008-03-07 9:48 ` David Howells [this message]
2008-03-07 14:29 ` David Howells
2008-03-07 16:01 ` Arun Raghavan
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=25831.1204883318@redhat.com \
--to=dhowells@redhat.com \
--cc=arunsr@cse.iitk.ac.in \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox