From: "David S. Miller" <davem@redhat.com>
To: James Morris <jmorris@redhat.com>
Cc: kuznet@ms2.inr.ac.ru, linux-security-module@wirex.com,
sds@epoch.ncsc.mil, netdev@oss.sgi.com
Subject: Re: [RFC] SO_PEERSEC - security credentials for Unix stream sockets
Date: Wed, 10 Dec 2003 14:56:52 -0800 [thread overview]
Message-ID: <20031210145652.66bda4c2.davem@redhat.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0312101110010.27922-100000@thoron.boston.redhat.com>
On Wed, 10 Dec 2003 11:33:53 -0500 (EST)
James Morris <jmorris@redhat.com> wrote:
> Three new LSM hooks have been implemented:
>
> - socket_getpeersec() is the getsockopt interface.
>
> - sk_alloc_security() and sk_free_security() facilitate the use of an
> sk_security field, which is used to store the security credentials of
> the Unix peer. We can't use an existing security field for this (e.g.
> inode), as we need the security credentials of the server's child
> socket. This follows the same general scheme used for managing existing
> Unix peer credentials.
>
> Comments?
I'm fine with this conceptually, although the earliest I could put
this into the tree is 2.6.1 although I have a hunch that I'll be
asked to defer something like this to 2.6.2, but who knows.
The one thing I don't like is the ifdef conditionalized member of
the sock struct. We should move away from config variables changing
structure layouts. Even a "void *sk_security;" would be better.
next prev parent reply other threads:[~2003-12-10 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 16:33 [RFC] SO_PEERSEC - security credentials for Unix stream sockets James Morris
2003-12-10 22:56 ` David S. Miller [this message]
2003-12-12 14:25 ` James Morris
2003-12-13 0:16 ` Chris Wright
2003-12-13 3:44 ` James Morris
2003-12-16 1:32 ` Chris Wright
2003-12-16 13:19 ` James Morris
2003-12-16 13:47 ` Stephen Smalley
2003-12-16 19:43 ` James Morris
2003-12-16 17:49 ` Chris Wright
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=20031210145652.66bda4c2.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-security-module@wirex.com \
--cc=netdev@oss.sgi.com \
--cc=sds@epoch.ncsc.mil \
/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).