1. 11 Nov, 2008 3 commits
  2. 08 Nov, 2008 1 commit
  3. 05 Nov, 2008 3 commits
    • Serge E. Hallyn's avatar
      file capabilities: add no_file_caps switch (v4) · 1f29fae2
      Serge E. Hallyn authored
      Add a no_file_caps boot option when file capabilities are
      compiled into the kernel (CONFIG_SECURITY_FILE_CAPABILITIES=y).
      This allows distributions to ship a kernel with file capabilities
      compiled in, without forcing users to use (and understand and
      trust) them.
      When no_file_caps is specified at boot, then when a process executes
      a file, any file capabilities stored with that file will not be
      used in the calculation of the process' new capability sets.
      This means that booting with the no_file_caps boot option will
      not be the same as booting a kernel with file capabilities
      compiled out - in particular a task with  CAP_SETPCAP will not
      have any chance of passing capabilities to another task (which
      isn't "really" possible anyway, and which may soon by killed
      altogether by David Howells in any case), and it will instead
      be able to put new capabilities in its pI.  However since fI
      will always be empty and pI is masked with fI, it gains the
      task nothing.
      We also support the extra prctl options, setting securebits and
      dropping capabilities from the per-process bounding set.
      The other remaining difference is that killpriv, task_setscheduler,
      setioprio, and setnice will continue to be hooked.  That will
      be noticable in the case where a root task changed its uid
      while keeping some caps, and another task owned by the new uid
      tries to change settings for the more privileged task.
      	Nov 05 2008: (v4) trivial port on top of always-start-\
      		with-clear-caps patch
      	Sep 23 2008: nixed file_caps_enabled when file caps are
      		not compiled in as it isn't used.
      		Document no_file_caps in kernel-parameters.txt.
      Signed-off-by: default avatarSerge Hallyn <serue@us.ibm.com>
      Acked-by: default avatarAndrew G. Morgan <morgan@kernel.org>
      Signed-off-by: default avatarJames Morris <jmorris@namei.org>
    • James Morris's avatar
      Merge branch 'master' into next · e21e696e
      James Morris authored
    • Michal Schmidt's avatar
      selinux: recognize netlink messages for 'ip addrlabel' · 2f99db28
      Michal Schmidt authored
      In enforcing mode '/sbin/ip addrlabel' results in a SELinux error:
      type=SELINUX_ERR msg=audit(1225698822.073:42): SELinux:  unrecognized
      netlink message type=74 for sclass=43
      The problem is missing RTM_*ADDRLABEL entries in SELinux's netlink
      message types table.
      Reported in https://bugzilla.redhat.com/show_bug.cgi?id=469423
      Signed-off-by: default avatarMichal Schmidt <mschmidt@redhat.com>
      Acked-by: default avatarStephen Smalley <sds@tycho.nsa.gov>
      Signed-off-by: default avatarJames Morris <jmorris@namei.org>
  4. 04 Nov, 2008 16 commits
  5. 03 Nov, 2008 17 commits