mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Dustin Kirkland <dustin.kirkland@us.ibm.com>,
	Linus Torvalds <torvalds@osdl.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH] Capture selinux subject/object context information.
Date: Mon, 27 Mar 2006 02:28:45 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0603270223540.2351@excalibur.intercode> (raw)
In-Reply-To: <200603251818.k2PIINcX027696@hera.kernel.org>

On Sat, 25 Mar 2006, Linux Kernel Mailing List wrote:

> commit 8c8570fb8feef2bc166bee75a85748b25cda22d9
> tree ed783d405ea9d5f3d3ccc57fb56c7b7cb2cdfb82
> parent c8edc80c8b8c397c53f4f659a05b9ea6208029bf
> author Dustin Kirkland <dustin.kirkland@us.ibm.com> Thu, 03 Nov 2005 17:15:16 +0000
> committer Al Viro <viro@zeniv.linux.org.uk> Tue, 21 Mar 2006 00:08:54 -0500
> 
> [PATCH] Capture selinux subject/object context information.
> 

> --- a/include/linux/security.h
> +++ b/include/linux/security.h
> @@ -869,6 +869,11 @@ struct swap_info_struct;
>   *	@ipcp contains the kernel IPC permission structure
>   *	@flag contains the desired (requested) permission set
>   *	Return 0 if permission is granted.
> + * @ipc_getsecurity:
> + *      Copy the security label associated with the ipc object into
> + *      @buffer.  @buffer may be NULL to request the size of the buffer 
> + *      required.  @size indicates the size of @buffer in bytes. Return 
> + *      number of bytes used/required on success.

I may have missed it, but was this change discussed on the LSM list?

> +	char *(*inode_xattr_getsuffix) (void);

Not documented?

>  static int selinux_inode_getsecurity(struct inode *inode, const char *name, void *buffer, size_t size, int err)

> -	if (err > 0) {
> -		if ((len == err) && !(memcmp(context, buffer, len))) {
> -			/* Don't need to canonicalize value */
> -			rc = err;
> -			goto out_free;
> -		}
> -		memset(buffer, 0, size);
> -	}

Where did this functionality go?



- James
-- 
James Morris
<jmorris@namei.org>

       reply	other threads:[~2006-03-27  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603251818.k2PIINcX027696@hera.kernel.org>
2006-03-27  7:28 ` James Morris [this message]
2006-03-27 14:16   ` Stephen Smalley

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=Pine.LNX.4.64.0603270223540.2351@excalibur.intercode \
    --to=jmorris@namei.org \
    --cc=chrisw@sous-sol.org \
    --cc=dustin.kirkland@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=torvalds@osdl.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®