1. 12 4月, 2010 13 次提交
  2. 09 4月, 2010 1 次提交
  3. 08 4月, 2010 2 次提交
  4. 16 3月, 2010 1 次提交
  5. 15 3月, 2010 1 次提交
  6. 10 3月, 2010 2 次提交
  7. 08 3月, 2010 1 次提交
  8. 05 3月, 2010 1 次提交
  9. 04 3月, 2010 4 次提交
  10. 03 3月, 2010 4 次提交
  11. 26 2月, 2010 2 次提交
  12. 25 2月, 2010 3 次提交
  13. 24 2月, 2010 1 次提交
    • W
      Security: add static to security_ops and default_security_ops variable · 189b3b1c
      wzt.wzt@gmail.com 提交于
      Enhance the security framework to support resetting the active security
      module. This eliminates the need for direct use of the security_ops and
      default_security_ops variables outside of security.c, so make security_ops
      and default_security_ops static. Also remove the secondary_ops variable as
      a cleanup since there is no use for that. secondary_ops was originally used by
      SELinux to call the "secondary" security module (capability or dummy),
      but that was replaced by direct calls to capability and the only
      remaining use is to save and restore the original security ops pointer
      value if SELinux is disabled by early userspace based on /etc/selinux/config.
      Further, if we support this directly in the security framework, then we can
      just use &default_security_ops for this purpose since that is now available.
      Signed-off-by: NZhitong Wang <zhitong.wangzt@alibaba-inc.com>
      Acked-by: NStephen Smalley <sds@tycho.nsa.gov>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      189b3b1c
  14. 22 2月, 2010 1 次提交
  15. 17 2月, 2010 1 次提交
  16. 16 2月, 2010 2 次提交