From: Chris Wright <chrisw@osdl.org>
To: James Morris <jmorris@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>,
kuznet@ms2.inr.ac.ru, linux-security-module@wirex.com,
Stephen Smalley <sds@epoch.ncsc.mil>,
netdev@oss.sgi.com
Subject: Re: [RFC] SO_PEERSEC - security credentials for Unix stream sockets
Date: Mon, 15 Dec 2003 17:32:41 -0800 [thread overview]
Message-ID: <20031215173241.B14552@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0312122219530.4813-100000@thoron.boston.redhat.com>; from jmorris@redhat.com on Fri, Dec 12, 2003 at 10:44:24PM -0500
* James Morris (jmorris@redhat.com) wrote:
> I'm not sure how this would be a namespace issue -- do you mean a data
> format issue?
I just mean, applications are coded for specific security module.
> Yep, allowing the security module to update the returned length is now
> implemented.
>
> > Perhaps buffer is too small, can len be vector for that info?
>
> I would not advise updating len on error -- it's a bad idea in general to
> interpret any returned data from failed syscalls except the error number.
Right, in some cases a NULL buffer or 0 buflen is a probe for size.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-12-16 1:32 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
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 [this message]
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=20031215173241.B14552@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=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).