Skip to content
  1. Aug 10, 2009
  3. Jun 28, 2009
  5. Jun 18, 2009
  7. Jun 08, 2009
  9. Jun 04, 2009
  11. Jun 03, 2009
  13. Jun 02, 2009
  15. May 28, 2009
  17. May 27, 2009
  19. May 26, 2009
  21. May 22, 2009
  23. May 21, 2009
    • Mimi Zohar's avatar
      integrity: path_check update · b9fc745d
      Mimi Zohar authored 
      

- Add support in ima_path_check() for integrity checking without
incrementing the counts. (Required for nfsd.)
- rename and export opencount_get to ima_counts_get
- replace ima_shm_check calls with ima_counts_get
- export ima_path_check

Signed-off-by: default avatarMimi Zohar <zohar@us.ibm.com>
Signed-off-by: default avatarJames Morris <jmorris@namei.org>
      b9fc745d
    • Eric Paris's avatar
      IMA: Add __init notation to ima functions · 932995f0
      Eric Paris authored 
      

A number of IMA functions only used during init are not marked with __init.
Add those notations so they are freed automatically.

Signed-off-by: default avatarEric Paris <eparis@redhat.com>
Acked-by: default avatarMimi Zohar <zohar@us.ibm.com>
Signed-off-by: default avatarJames Morris <jmorris@namei.org>
      932995f0
    • Eric Paris's avatar
      IMA: Minimal IMA policy and boot param for TCB IMA policy · 5789ba3b
      Eric Paris authored 
      

The IMA TCB policy is dangerous.  A normal use can use all of a system's
memory (which cannot be freed) simply by building and running lots of
executables.  The TCB policy is also nearly useless because logging in as root
often causes a policy violation when dealing with utmp, thus rendering the
measurements meaningless.

There is no good fix for this in the kernel.  A full TCB policy would need to
be loaded in userspace using LSM rule matching to get both a protected and
useful system.  But, if too little is measured before userspace can load a real
policy one again ends up with a meaningless set of measurements.  One option
would be to put the policy load inside the initrd in order to get it early
enough in the boot sequence to be useful, but this runs into trouble with the
LSM.  For IMA to measure the LSM policy and the LSM policy loading mechanism
it needs rules to do so, but we already talked about problems with defaulting
to such broad rules....

IMA also depends on the files being measured to be on an FS which implements
and supports i_version.  Since the only FS with this support (ext4) doesn't
even use it by default it seems silly to have any IMA rules by default.

This should reduce the performance overhead of IMA to near 0 while still
letting users who choose to configure their machine as such to inclue the
ima_tcb kernel paramenter and get measurements during boot before they can
load a customized, reasonable policy in userspace.

Signed-off-by: default avatarEric Paris <eparis@redhat.com>
Acked-by: default avatarMimi Zohar <zohar@us.ibm.com>
Signed-off-by: default avatarJames Morris <jmorris@namei.org>
      5789ba3b
  25. May 19, 2009
    • Stephen Smalley's avatar
      selinux: remove obsolete read buffer limit from sel_read_bool · c5642f4b
      Stephen Smalley authored 
      

On Tue, 2009-05-19 at 00:05 -0400, Eamon Walsh wrote:
> Recent versions of coreutils have bumped the read buffer size from 4K to
> 32K in several of the utilities.
>
> This means that "cat /selinux/booleans/xserver_object_manager" no longer
> works, it returns "Invalid argument" on F11.  getsebool works fine.
>
> sel_read_bool has a check for "count > PAGE_SIZE" that doesn't seem to
> be present in the other read functions.  Maybe it could be removed?

Yes, that check is obsoleted by the conversion of those functions to
using simple_read_from_buffer(), which will reduce count if necessary to
what is available in the buffer.

Signed-off-by: default avatarStephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: default avatarJames Morris <jmorris@namei.org>
      c5642f4b
  27. May 18, 2009
  29. May 14, 2009
  31. May 12, 2009
  33. May 09, 2009
  35. May 06, 2009
  37. May 04, 2009
  39. Apr 29, 2009
  41. Apr 18, 2009
  43. Apr 15, 2009