1. 12 4月, 2015 2 次提交
  2. 30 4月, 2013 1 次提交
  3. 12 10月, 2012 1 次提交
  4. 21 9月, 2012 1 次提交
  5. 15 5月, 2012 1 次提交
  6. 15 3月, 2012 1 次提交
  7. 04 1月, 2012 1 次提交
  8. 12 12月, 2011 1 次提交
  9. 26 9月, 2011 3 次提交
  10. 19 9月, 2011 1 次提交
    • T
      TOMOYO: Allow specifying domain transition preference. · 6bce98ed
      Tetsuo Handa 提交于
      I got an opinion that it is difficult to use exception policy's domain
      transition control directives because they need to match the pathname specified
      to "file execute" directives. For example, if "file execute /bin/\*\-ls\-cat"
      is given, corresponding domain transition control directive needs to be like
      "no_keep_domain /bin/\*\-ls\-cat from any".
      
      If we can specify like below, it will become more convenient.
      
        file execute /bin/ls keep exec.realpath="/bin/ls" exec.argv[0]="ls"
        file execute /bin/cat keep exec.realpath="/bin/cat" exec.argv[0]="cat"
        file execute /bin/\*\-ls\-cat child
        file execute /usr/sbin/httpd <apache> exec.realpath="/usr/sbin/httpd" exec.argv[0]="/usr/sbin/httpd"
      
      In above examples, "keep" works as if keep_domain is specified, "child" works
      as if "no_reset_domain" and "no_initialize_domain" and "no_keep_domain" are
      specified, "<apache>" causes domain transition to <apache> domain upon
      successful execve() operation.
      
      Moreover, we can also allow transition to different domains based on conditions
      like below example.
      
        <kernel> /usr/sbin/sshd
        file execute /bin/bash <kernel> /usr/sbin/sshd //batch-session exec.argc=2 exec.argv[1]="-c"
        file execute /bin/bash <kernel> /usr/sbin/sshd //root-session task.uid=0
        file execute /bin/bash <kernel> /usr/sbin/sshd //nonroot-session task.uid!=0
      Signed-off-by: NTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      6bce98ed
  11. 15 9月, 2011 1 次提交
  12. 14 9月, 2011 4 次提交
  13. 11 7月, 2011 5 次提交
  14. 08 7月, 2011 1 次提交
  15. 30 6月, 2011 1 次提交
  16. 29 6月, 2011 13 次提交
  17. 27 9月, 2010 1 次提交
  18. 02 8月, 2010 1 次提交
    • T
      TOMOYO: Use pathname specified by policy rather than execve() · 484ca79c
      Tetsuo Handa 提交于
      Commit c9e69318 "TOMOYO: Allow wildcard for execute permission." changed execute
      permission and domainname to accept wildcards. But tomoyo_find_next_domain()
      was using pathname passed to execve() rather than pathname specified by the
      execute permission. As a result, processes were not able to transit to domains
      which contain wildcards in their domainnames.
      
      This patch passes pathname specified by the execute permission back to
      tomoyo_find_next_domain() so that processes can transit to domains which
      contain wildcards in their domainnames.
      Signed-off-by: NTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      484ca79c