All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] keys & keyring management update patch
Date: Wed, 18 Aug 2004 15:07:33 +0100	[thread overview]
Message-ID: <22380.1092838053@redhat.com> (raw)


I've made available a patch that makes some alterations to my key management
stuff, mainly to support keyfs. The patch can be downloaded from:

    http://people.redhat.com/~dhowells/keys/keys-268rc4mm1.diff.bz2
    Signed-Off-By: David Howells <dhowells@redhat.com>

To summarise the changes in this patch:

 (*) There are now five permissions instead of three, which makes things
     easier. Hopefully it also means that people will stop thinking keys have
     UNIX access permissions, which they do not.

 (*) The key "chmod" operation is now "setperm".

 (*) fsuid/fsgid are now used instead of euid/egid when using permissions.

 (*) Some stuff has been moved from the internal header file into
     include/linux/key-ui.h to make it available to keyfs.

 (*) /proc/keys is now disabled by default. It pretends keys don't exist
     unless you have at least one permission on them.

David

                 reply	other threads:[~2004-08-18 14:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=22380.1092838053@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.