From: David Howells <dhowells@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: dhowells@redhat.com,
Stefan Schulze Frielinghaus <stefan@seekline.net>,
selinux@tycho.nsa.gov
Subject: Re: [Fwd: type class key]
Date: Thu, 15 Nov 2007 13:08:24 +0000 [thread overview]
Message-ID: <24667.1195132104@redhat.com> (raw)
In-Reply-To: <1194638426.624.91.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley <sds@tycho.nsa.gov> wrote:
> Ah, wait - this is an automatic allocation of a per-uid keyring upon a
> setuid() call, right?
Maybe that's the solution: Don't automatically allocate the per-UID keyrings
until someone tries to link to one or put something into one.
Searching the keyrings won't create them - there's no point as they'd be empty
anyway.
The pam_keyinit module could then be made to take a "nouser" argument that
would tell it to avoid making the link from the session keyring it creates to
the user keyring (or conversely a "user" argument that tells it to create the
link).
That way I can arrange for only login processes (login, ssh, kdm, gdm, telnet,
etc) to use the per-UID keyrings. Things such as dovecot wouldn't then use
it and so wouldn't create it.
David
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2007-11-15 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1194628263.3630.14.camel@vogon>
[not found] ` <1194554589.3198.24.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <24708.1194612682@redhat.com>
[not found] ` <22421.1194637689@redhat.com>
2007-11-09 19:51 ` [Fwd: type class key] Stephen Smalley
2007-11-09 20:00 ` Stephen Smalley
2007-11-09 20:35 ` Casey Schaufler
2007-11-10 12:26 ` David Howells
2007-11-14 20:23 ` Daniel J Walsh
2007-11-15 12:17 ` David Howells
2007-11-15 13:33 ` Daniel J Walsh
2007-11-15 13:57 ` Stephen Smalley
2007-11-15 14:41 ` David Howells
2007-11-15 14:52 ` Stephen Smalley
2007-11-15 14:53 ` David Howells
2007-11-15 14:56 ` Stephen Smalley
2007-11-15 14:58 ` David Howells
2007-11-15 15:02 ` Stephen Smalley
2007-11-15 16:04 ` David Howells
2007-11-15 17:34 ` David Howells
2007-11-15 18:26 ` Stephen Smalley
2007-11-15 19:04 ` David Howells
2007-11-16 19:53 ` Casey Schaufler
2007-11-15 20:40 ` James Morris
2007-11-15 13:08 ` David Howells [this message]
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=24667.1195132104@redhat.com \
--to=dhowells@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=stefan@seekline.net \
/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.