linux-kernel - Re: [Patch 7/7] IBAC Patch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 22 Mar 2007 23:10:12 +0000
From:	Pavel Machek <pavel@....cz>
To:	"Serge E. Hallyn" <serge@...lyn.com>
Cc:	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, safford@...son.ibm.com,
	serue@...ux.vnet.ibm.com, kjhall@...ux.vnet.ibm.com,
	zohar@...ibm.com, akpm@...l.org
Subject: Re: [Patch 7/7] IBAC Patch

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@...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?
> 
> I assume, as it says not too far above, we want it as
> 
> 	"a sample LSM module to help clarify the interaction between LSM
> 	and Linux Integrity Modules(LIM)"
> 
> Since the LIM stuff is infrastructure code, a simple user is nice of her
> to provide, like the root_plug LSM.
> 
> Perhaps the comments should warn that using this for real by itself
> would be trivial to work around?

Certainly. And I'm not sure if we are not carying enough example code
already :-).
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/