mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, safford@watson.ibm.com,
	serue@linux.vnet.ibm.com, kjhall@linux.vnet.ibm.com,
	zohar@us.ibm.com, akpm@osdl.org
Subject: Re: [Patch 7/7] IBAC Patch
Date: Sun, 25 Mar 2007 12:38:50 +0000	[thread overview]
Message-ID: <20070325123849.GB8550@ucw.cz> (raw)
In-Reply-To: <1174666224.11149.7.camel@localhost.localdomain>

Hi!

> This is a new Integrity Based Access Control(IBAC) LSM module which 
> bases access control decisions on the new integrity framework services. 
> IBAC is a sample LSM module to help clarify the interaction between 
> LSM and Linux Integrity Modules(LIM).
> 
>    - Updated Kconfig SECURITY_IBAC description
>      and SECURITY_IBAC_BOOTPARAM default value
>    - Prefixed all log messages with "ibac:"
>    - Redefined a couple of 'int' variables as 'static int'
> 
> signed-off-by: Mimi Zohar <zohar@us.ibm.com>
> ---
> Index: linux-2.6.21-rc4-mm1/security/ibac/Kconfig
> ===================================================================
> --- /dev/null
> +++ linux-2.6.21-rc4-mm1/security/ibac/Kconfig
> @@ -0,0 +1,41 @@
> +config SECURITY_IBAC
> +	boolean "IBAC support"
> +	depends on SECURITY && SECURITY_NETWORK && INTEGRITY
> +	help
> +	  Integrity Based Access Control(IBAC) uses the Linux
> +	  Integrity Module(LIM) API calls to verify an executable's
> +	  metadata and data's integrity.  Based on the results,
> +	  execution permission is permitted/denied.  Integrity
> +	  providers may implement the LIM hooks differently.  For
> +	  more information on integrity verification refer to the
> +	  specific integrity provider documentation.

...sounds like pseudosecurity piece of **** whose only purpose is to
prevent computer's owner to hack his own system?

Why do we want it?
						Pavel


> + * Integrity Based Access Control(IBAC) sample LSM module calling LIM hooks

sample?

> +static inline int is_kernel_thread(struct task_struct *tsk)
> +{
> +	return (!tsk->mm) ? 1 : 0;
> +}

Obfuscated C code contest?

						Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-03-25 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 16:10 Mimi Zohar
2007-03-25 12:38 ` Pavel Machek [this message]
2007-03-25 16:31   ` Serge E. Hallyn
2007-03-22 23:10     ` Pavel Machek

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=20070325123849.GB8550@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=kjhall@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safford@watson.ibm.com \
    --cc=serue@linux.vnet.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    --cc=zohar@us.ibm.com \
    /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®