16 |
|
|
17 |
This project was very inspired by the comic "Card Captor SAKURA", |
This project was very inspired by the comic "Card Captor SAKURA", |
18 |
one of the CLAMP's masterworks. |
one of the CLAMP's masterworks. |
|
The names SAKURA and TOMOYO and SYAORAN were borrowed from the comic |
|
|
with the heartfelt thanks to CLAMP. |
|
|
|
|
|
|
|
19 |
|
|
20 |
ChangeLog: |
ChangeLog: |
21 |
|
|
193 |
@ Fix handling of trailing '\*' in PathMatchesToPattern(). |
@ Fix handling of trailing '\*' in PathMatchesToPattern(). |
194 |
|
|
195 |
PathMatchesToPattern("/tmp/", "/tmp/\*") returned true |
PathMatchesToPattern("/tmp/", "/tmp/\*") returned true |
196 |
because "\*" matches to "more than or equals to 0 character |
because "\*" matches "zero or more repetitions of characters |
197 |
until '/' or end". But since this is a comparison between |
until '/' or end". But since this is a comparison between |
198 |
directory and non-directory, this should not match. |
directory and non-directory, this should not match. |
199 |
|
|
404 |
|
|
405 |
@ Change behavior of pathname pattern matching. |
@ Change behavior of pathname pattern matching. |
406 |
|
|
407 |
Until now, it was impossible to use patterns like "\*.txt" |
Until now, it was impossible to use patterns like "\*.txt" because |
408 |
because "\*" matched to more than 0 characters until next '/'. |
"\*" matched zero or more repetitions of characters until next '/'. |
409 |
Now, "\*" matches to more than 0 characters. |
Now, "\*" matches zero or more repetitions of characters. |
410 |
|
|
411 |
Until now, it was impossible to use patterns like "\$00" |
Until now, it was impossible to use patterns like "\$00" |
412 |
because "\$" matched to more than 1 digits until next |
because "\$" matched one or more repetitions of digits until next |
413 |
non digit character. |
non digit character. |
414 |
Now, "\$" matches to more than 1 digits. |
Now, "\$" matches one or more repetitions of digits. |
415 |
|
|
416 |
Also, new patterns "\x" "\X" "\a" "\A" "\@" are added. |
Also, new patterns "\x" "\X" "\a" "\A" "\@" are added. |
417 |
|
|
428 |
|
|
429 |
@ Change matching rule for CheckFileACL(). |
@ Change matching rule for CheckFileACL(). |
430 |
|
|
431 |
Until now, only first entry that matched to the requested pathname |
Until now, only first entry that matched the requested pathname |
432 |
was used for permission checking. For example, two entries |
was used for permission checking. For example, two entries |
433 |
|
|
434 |
"2 /tmp/file-\$.txt" |
"2 /tmp/file-\$.txt" |
444 |
This may potentially cause trouble because the result of |
This may potentially cause trouble because the result of |
445 |
permission checks depends on the order of entries. |
permission checks depends on the order of entries. |
446 |
|
|
447 |
Now, all entries that matched to the requested pathname |
Now, all entries that matched the requested pathname |
448 |
are used for permission checking so that the result of |
are used for permission checking so that the result of |
449 |
permission checks doesn't depend on the order of entries. |
permission checks doesn't depend on the order of entries. |
450 |
|
|
485 |
domain ACL. For example, |
domain ACL. For example, |
486 |
|
|
487 |
"1 /bin/sh if task.euid!=0" |
"1 /bin/sh if task.euid!=0" |
488 |
|
|
489 |
allows the domain to execute /bin/sh only when the process's euid |
allows the domain to execute /bin/sh only when the process's euid |
490 |
is not 0, and |
is not 0, and |
491 |
|
|
492 |
"6 /home/\*/\* if task.uid=path1.uid" |
"6 /home/\*/\* if task.uid=path1.uid" |
493 |
|
|
494 |
allows the domain to read-write user's home directory |
allows the domain to read-write user's home directory |
495 |
only when the file's owner matches to the process's uid. |
only when the file's owner matches the process's uid. |
496 |
|
|
497 |
Fix 2006/08/22 |
Fix 2006/08/22 |
498 |
|
|
758 |
if /some/program is called from "some_domain" domain. |
if /some/program is called from "some_domain" domain. |
759 |
|
|
760 |
"some_domain" can be just the last component of domainname. |
"some_domain" can be just the last component of domainname. |
761 |
For example, giving "/bin/mail" as "some_domain" matches to |
For example, giving "/bin/mail" as "some_domain" matches |
762 |
all domains whose domainname ends with "/bin/mail". |
all domains whose domainname ends with "/bin/mail". |
763 |
|
|
764 |
Fix 2007/01/19 |
Fix 2007/01/19 |
871 |
based on realpath while argv[0] check is done based on the symlink's |
based on realpath while argv[0] check is done based on the symlink's |
872 |
pathname and argv[0], this specification will allow attackers behave |
pathname and argv[0], this specification will allow attackers behave |
873 |
as /bin/cat in the domain of /bin/ls if "/bin/ls and /bin/cat are |
as /bin/cat in the domain of /bin/ls if "/bin/ls and /bin/cat are |
874 |
links to /sbin/busybox" and "the attacker is permitted to create |
links to /sbin/busybox" and "the attacker is permitted to create |
875 |
a symlink named ~/cat that points to /bin/ls" and "the attacker is |
a symlink named ~/cat that points to /bin/ls" and "the attacker is |
876 |
permitted to run /bin/ls". |
permitted to run /bin/ls". |
877 |
So, I changed to compare the basename of realpath and argv[0]. |
So, I changed to compare the basename of realpath and argv[0]. |
959 |
|
|
960 |
Until now, users had to add init=/.init parameter to load policy |
Until now, users had to add init=/.init parameter to load policy |
961 |
before /sbin/init starts. |
before /sbin/init starts. |
962 |
I inserted call_usermodehelper() to call external policy loader when |
I inserted call_usermodehelper() to call external policy loader when |
963 |
execve("/sbin/init") is requested and external policy loader exists. |
execve("/sbin/init") is requested and external policy loader exists. |
964 |
|
|
965 |
This change will remove init=/.init parameter from most environment, |
This change will remove init=/.init parameter from most environment, |
1003 |
|
|
1004 |
@ Remove initializer directive. |
@ Remove initializer directive. |
1005 |
|
|
1006 |
Use "initialize_domain" instrad of "initializer". |
Use "initialize_domain" instead of "initializer". |
1007 |
|
|
1008 |
Fix 2007/08/21 |
Fix 2007/08/21 |
1009 |
|
|
1749 |
new conditions for checking file's type and permissions. |
new conditions for checking file's type and permissions. |
1750 |
For example, |
For example, |
1751 |
|
|
1752 |
allow_read /etc/fstab if path1.type=regular path1.perm=0644 |
allow_read /etc/fstab if path1.type=file path1.perm=0644 |
1753 |
|
|
1754 |
will allow opening /etc/fstab for reading only if /etc/fstab is a regular |
will allow opening /etc/fstab for reading only if /etc/fstab is a regular |
1755 |
file and it's permission is 0644, and |
file and it's permission is 0644, and |
1800 |
As remove_arg_zero() uses kmap_atomic(KM_USER0), I modified to use |
As remove_arg_zero() uses kmap_atomic(KM_USER0), I modified to use |
1801 |
kmap_atomic(KM_USER0) rather than kmap(). |
kmap_atomic(KM_USER0) rather than kmap(). |
1802 |
|
|
|
@ Relocate definitions and functions. |
|
|
|
|
|
To reduce exposed symbols, I relocated some definitions and functions. |
|
|
|
|
1803 |
Fix 2009/01/28 |
Fix 2009/01/28 |
1804 |
|
|
1805 |
@ Fix "allow_read" + "allow_write" != "allow_read/write" problem. |
@ Fix "allow_read" + "allow_write" != "allow_read/write" problem. |
1810 |
but open(O_RDONLY) and open(O_WRONLY) fail. |
but open(O_RDONLY) and open(O_WRONLY) fail. |
1811 |
|
|
1812 |
Workaround is to write an entry twice when newly appending that entry. |
Workaround is to write an entry twice when newly appending that entry. |
1813 |
If written twice, internal "allow_read" and "allow_write" entries |
If written twice, internal "allow_read" and "allow_write" entries |
1814 |
are updated. |
are updated. |
1815 |
|
|
1816 |
|
Fix 2009/02/26 |
1817 |
|
|
1818 |
|
@ Fix profile read error. |
1819 |
|
|
1820 |
|
Incorrect profiles were shown in /proc/ccs/profile |
1821 |
|
if either CONFIG_SAKURA or CONFIG_TOMOYO is disabled. |
1822 |
|
|
1823 |
|
Fix 2009/03/02 |
1824 |
|
|
1825 |
|
@ Undelete CONFIG_TOMOYO_AUDIT option. |
1826 |
|
|
1827 |
|
While HDD-less systems can use profiles with MAX_GRANT_LOG=0 and |
1828 |
|
MAX_REJECT_LOG=0 , I undeleted CONFIG_TOMOYO_AUDIT option for saving |
1829 |
|
memory used for /proc/ccs/grant_log and /proc/ccs/reject_log interfaces. |
1830 |
|
|
1831 |
|
Fix 2009/03/13 |
1832 |
|
|
1833 |
|
@ Show only profile entry names ever specified. |
1834 |
|
|
1835 |
|
Even if an administrator specifies only COMMENT= and MAC_FOR_FILE= |
1836 |
|
entries for /proc/ccs/profile , all available profile entries are shown. |
1837 |
|
This was designed to help administrators to know what entries are |
1838 |
|
available, but sometimes makes administrators feel noisy because of |
1839 |
|
entries showing default values. |
1840 |
|
|
1841 |
|
Thus, I modified to show only profile entry names ever specified. |
1842 |
|
|
1843 |
|
Fix 2009/03/18 |
1844 |
|
|
1845 |
|
@ Add MAC_FOR_IOCTL functionality. |
1846 |
|
|
1847 |
|
To be able to restrict ioctl() requests, I added MAC_FOR_IOCTL |
1848 |
|
functionality. |
1849 |
|
|
1850 |
|
This functionality requires modification of ccs-patch-\*.diff . |
1851 |
|
|
1852 |
|
@ Use better name for socket's pathname. |
1853 |
|
|
1854 |
|
Until now, socket's pathname was represented as "socket:[\$]" format |
1855 |
|
where \$ is inode's number. But inode's number is useless for name based |
1856 |
|
access control. Therefore, I modified to represent socket's pathname as |
1857 |
|
"socket:[family=\$:type=\$:protocol=\$]" format. |
1858 |
|
|
1859 |
|
This will help administrator to control ioctl() against sockets more |
1860 |
|
precisely. |
1861 |
|
|
1862 |
|
@ Fix misplaced ccs_capable() call. (only 2.6.8-\* and 2.6.9-\*) |
1863 |
|
|
1864 |
|
Location to insert ccs_capable(TOMOYO_SYS_IOCTL) in sys_ioctl() was |
1865 |
|
wrong since version 1.1 . |
1866 |
|
|
1867 |
|
@ Insert ccs_check_ioctl_permission() call. |
1868 |
|
|
1869 |
|
To make MAC_FOR_IOCTL functionality working, I inserted |
1870 |
|
ccs_check_ioctl_permission() call into ccs-patch-\*.diff . |
1871 |
|
|
1872 |
|
Fix 2009/03/23 |
1873 |
|
|
1874 |
|
@ Move sysctl()'s check from ccs-patch-\*.diff to fs/tomoyo_file.c . |
1875 |
|
|
1876 |
|
Since try_parse_table() in kernel/sysctl.c is almost identical between |
1877 |
|
all versions, I moved that function to fs/tomoyo_file.c . |
1878 |
|
|
1879 |
|
@ Relocate definitions and functions. |
1880 |
|
|
1881 |
|
To reduce exposed symbols, I relocated some definitions and functions. |
1882 |
|
|
1883 |
|
Fix 2009/03/24 |
1884 |
|
|
1885 |
|
@ Add CONFIG_TOMOYO_BUILTIN_INITIALIZERS option. |
1886 |
|
|
1887 |
|
Some systems don't have /sbin/modprobe and /sbin/hotplug . |
1888 |
|
Thus, I made these pathnames configurable. |
1889 |
|
|
1890 |
|
Version 1.6.7 2009/04/01 Feature enhancement release. |
1891 |
|
|
1892 |
|
Fix 2009/04/06 |
1893 |
|
|
1894 |
|
@ Drop "undelete domain" command. |
1895 |
|
|
1896 |
|
I added "undelete domain" command on 2007/01/19, but never used by policy |
1897 |
|
management tools. The garbage collector I added on 2007/01/29 will |
1898 |
|
automatically reuse memory and allow administrators switch domain policy |
1899 |
|
periodically, provided that the administrator kills processes in old |
1900 |
|
domains before recreating new domains with the same domainnames. |
1901 |
|
|
1902 |
|
Thus, I dropped "undelete domain" command. |
1903 |
|
|
1904 |
|
@ Escape invalid characters in ccs_check_mount_permission2(). |
1905 |
|
|
1906 |
|
ccs_check_mount_permission2() was passing unencoded strings to printk() |
1907 |
|
and ccs_update_mount_acl() and ccs_check_supervisor(). This may cause |
1908 |
|
/proc/ccs/system_policy and /proc/ccs/query to contain invalid |
1909 |
|
characters within a string. |
1910 |
|
|
1911 |
|
Fix 2009/04/07 |
1912 |
|
|
1913 |
|
@ Fix IPv4's "address_group" handling error. |
1914 |
|
|
1915 |
|
Since 1.6.5 , due to lack of ntohl() (byte order conversion) in |
1916 |
|
ccs_update_address_group_entry(), "address_group" with IPv4 address was |
1917 |
|
not working. |
1918 |
|
|
1919 |
|
This problem happens on little endian platforms (e.g. x86). |
1920 |
|
|
1921 |
|
Fix 2009/05/08 |
1922 |
|
|
1923 |
|
@ Add condition for symlink's target pathname. |
1924 |
|
|
1925 |
|
Until now, "allow_symlink" keyword allows creation of a symlink but does |
1926 |
|
not check the symlink's target. Usually it is no problem because |
1927 |
|
permission checks are done using dereferenced pathname. But in some |
1928 |
|
cases, we should restrict the symlink's target. For example, |
1929 |
|
"ln -s .htpasswd /var/www/html/readme.html" by CGI program should be |
1930 |
|
blocked because we will allow Apache to read both |
1931 |
|
/var/www/html/readme.html and /var/www/html/.htpasswd . |
1932 |
|
|
1933 |
|
Thus, I added new condition, "symlink.target". |
1934 |
|
|
1935 |
|
allow_symlink /var/www/html/\*.html if symlink.target="\*.html" |
1936 |
|
|
1937 |
|
allow_symlink /var/www/html/\*\-.\* if symlink.target="\*\-.\*" |
1938 |
|
|
1939 |
|
@ Don't return -EAGAIN at ccs_socket_recvmsg_permission(). |
1940 |
|
|
1941 |
|
It turned out that it is not permitted for accept() and recvmsg() to |
1942 |
|
return -EAGAIN if poll() said connections/datagrams are ready. However, |
1943 |
|
recvmsg() may return -EAGAIN and potentially confuse some applications |
1944 |
|
because ccs_socket_recvmsg_permission() is returning -EAGAIN. |
1945 |
|
|
1946 |
|
Thus, I modified ccs_socket_recvmsg_permission() to return -ENOMEM |
1947 |
|
rather than -EAGAIN. |
1948 |
|
|
1949 |
|
Fix 2009/05/19 |
1950 |
|
|
1951 |
|
@ Don't call get_fs_type() with a mutex held. |
1952 |
|
|
1953 |
|
Until now, when ccs_update_mount_acl() is called with unsupported |
1954 |
|
filesystem, /sbin/modprobe is executed from get_fs_type() to load |
1955 |
|
filesystem module. And get_fs_type() does not return until /sbin/modprobe |
1956 |
|
finishes. |
1957 |
|
|
1958 |
|
This means that it will cause deadlock if /sbin/modprobe (which is |
1959 |
|
executed via get_fs_type() in ccs_update_mount_acl()) calls |
1960 |
|
ccs_update_mount_acl(); although it won't happen unless an administrator |
1961 |
|
inserts execute_handler to call mount() requests in learning mode or to |
1962 |
|
add "allow_mount" entries to /proc/ccs/system_policy . |
1963 |
|
|
1964 |
|
I modified to unlock the mutex before calling get_fs_type(). |
1965 |
|
|
1966 |
|
Fix 2009/05/20 |
1967 |
|
|
1968 |
|
@ Update recvmsg() hooks. |
1969 |
|
|
1970 |
|
Since 1.5.0, I was doing network access control for incoming UDP and RAW |
1971 |
|
packets inside skb_recv_datagram(). But to synchronize with LSM version, |
1972 |
|
I moved ccs_recv_datagram_permission() hook from skb_recv_datagram() to |
1973 |
|
udp_recvmsg()/udpv6_recvmsg()/raw_recvmsg()/rawv6_recvmsg() with name |
1974 |
|
change to ccs_recvmsg_permission(). |
1975 |
|
|
1976 |
|
Version 1.6.8 2009/05/28 Feature enhancement release. |
1977 |
|
|
1978 |
|
Fix 2009/07/03 |
1979 |
|
|
1980 |
|
@ Fix buffer overrun when used with CONFIG_SLOB=y . |
1981 |
|
|
1982 |
|
Since 1.6.7 , ccs_allocate_execve_entry() was requesting for only 4000 |
1983 |
|
bytes while the comment says it is 4096 bytes. This may lead to buffer |
1984 |
|
overrun when slob allocator is used, for slob allocator allocates exactly |
1985 |
|
4000 bytes whereas slab and slub allocators allocate 4096 bytes. |
1986 |
|
|
1987 |
|
Fix 2009/09/01 |
1988 |
|
|
1989 |
|
@ Add garbage collector support. |
1990 |
|
|
1991 |
|
Until now, it was impossible to release memory used by deleted policy. |
1992 |
|
I added SRCU based garbage collector so that memory used by deleted |
1993 |
|
policy will be automatically released. |
1994 |
|
|
1995 |
|
@ Remove word length limitation and line length limitation. |
1996 |
|
|
1997 |
|
Until now, the max length of a word is 4000 and the max length of a line |
1998 |
|
is 8192. To be able to handle longer pathnames, I removed these |
1999 |
|
limitations. Now, the max length (except the domainname and |
2000 |
|
argv[]/envp[]) is 128K (which is the max amount of memory kmalloc() |
2001 |
|
can allocate in most environments). |
2002 |
|
|
2003 |
|
@ Support more fine grained profile configuration. |
2004 |
|
|
2005 |
|
Profile was reconstructed. |
2006 |
|
|
2007 |
|
@ Support more fine grained parameters restrictions. |
2008 |
|
|
2009 |
|
"allow_create", "allow_mkdir", "allow_mkfifo", "allow_mksock" check |
2010 |
|
create mode. "allow_mkblock" and "allow_mkchar" check create mode and |
2011 |
|
major/minor device numbers. "allow_chmod" check new mode. "allow_chown" |
2012 |
|
checks new owner. "allow_chgrp" checks new group. |
2013 |
|
|
2014 |
|
@ Allow number grouping. |
2015 |
|
|
2016 |
|
To help specifying numeric values, a new directive "number_group" is |
2017 |
|
introduced. |
2018 |
|
|
2019 |
|
@ Remove "alias" directive and "allow_argv0" directive. |
2020 |
|
|
2021 |
|
Until now, "allow_execute" used dereferenced pathname if it is a symlink |
2022 |
|
unless explicitly specified by "alias" directive. |
2023 |
|
|
2024 |
|
Now, "allow_execute" uses symlink's pathname if it is a symlink. |
2025 |
|
"exec.realpath" in "if" clause checks the dereferenced pathname. |
2026 |
|
"exec.argv[0]" in "if" clause checks the invocation name. |
2027 |
|
|
2028 |
|
@ Remove /proc/ccs/system_policy and /etc/ccs/system_policy.conf . |
2029 |
|
|
2030 |
|
"deny_autobind" was moved to /proc/ccs/exception_policy and |
2031 |
|
/etc/ccs/exception_policy.conf . Other directives were moved to |
2032 |
|
/proc/ccs/domain_policy and /etc/ccs/domain_policy.conf . |
2033 |
|
|
2034 |
|
@ Remove syaoran filesystem. |
2035 |
|
|
2036 |
|
Since "allow_create"/"allow_mkdir"/"allow_mkfifo"/"allow_mksock"/ |
2037 |
|
"allow_mkblock"/"allow_mkchar"/"allow_chmod"/"allow_chown"/"allow_chgrp" |
2038 |
|
can restrict mode changes and owner/group changes, there is no need to |
2039 |
|
restrict these changes at filesystem level. |
2040 |
|
|
2041 |
|
Thus, I removed syaoran filesystem. |
2042 |
|
|
2043 |
|
@ Reduce spinlocks. |
2044 |
|
|
2045 |
|
Until now, TOMOYO was using own list for detecting memory leak. But as |
2046 |
|
kernel 2.6.31 introduced memory leak detection mechanism |
2047 |
|
( CONFIG_DEBUG_KMEMLEAK ), TOMOYO no longer needs to use own list. |
2048 |
|
|
2049 |
|
I removed the list to reduce use of spinlocks. |
2050 |
|
|
2051 |
|
@ Rewrite ccs-patch-2.\*.diff . |
2052 |
|
|
2053 |
|
ccs-patch-2.\*.diff was rewritten like LSM hooks. |
2054 |
|
|
2055 |
|
@ Don't check "allow_read/write" for open-for-ioctl-only. |
2056 |
|
|
2057 |
|
open(pathname, 3) means open for ioctl() only. |
2058 |
|
Until now, TOMOYO was checking "allow_read/write" for open(pathname, 3). |
2059 |
|
But since TOMOYO checks "allow_ioctl" for ioctl(), I modified not to |
2060 |
|
require "allow_read/write" for open(pathname, 3). |
2061 |
|
|
2062 |
|
@ Add missing sigqueue() and tgsigqueue() hooks. |
2063 |
|
|
2064 |
|
Until now, kill(), tkill(), tgkill() had hooks but sigqueue() and |
2065 |
|
tgsigqueue() didn't. |
2066 |
|
|
2067 |
|
@ Move files from fs/ to security/ccsecurity. |
2068 |
|
|
2069 |
|
Config menu section changed from "File systems" to "Security options". |
2070 |
|
|
2071 |
|
Kernel config symbols changed from CONFIG_SAKURA CONFIG_TOMOYO |
2072 |
|
CONFIG_SYAORAN to CONFIG_CCSECURITY . |
2073 |
|
|
2074 |
|
@ Add global PID to audit logs. |
2075 |
|
|
2076 |
|
ccs-queryd was using domainname for reaching the domain which the process |
2077 |
|
belongs to, but the domain could be deleted while ccs-queryd is handling |
2078 |
|
policy violation. If the domain is deleted, ccs-queryd no longer can |
2079 |
|
reach the domain by domainname. Thus, ccs-queryd now uses PID for |
2080 |
|
reaching the domain which the process belongs to. |
2081 |
|
|
2082 |
|
Kernel 2.6.24 introduced PID namespace. The PID in access logs generated |
2083 |
|
by a process inside a container is useless for ccs-queryd for reaching |
2084 |
|
the domain which the process belongs to. |
2085 |
|
|
2086 |
|
Thus, I added global PID in audit logs. |
2087 |
|
|
2088 |
|
@ Transit to new domain before do_execve() succeeds. |
2089 |
|
|
2090 |
|
Permission checks for interpreters and environment variables are |
2091 |
|
done using new domain. In order to allow ccs-queryd to reach the new |
2092 |
|
domain via global PID, I reverted "Don't transit to new domain until |
2093 |
|
do_execve() succeeds." made on 2008/10/07. |
2094 |
|
|
2095 |
|
Version 1.7.0 2009/09/03 Feature enhancement release. |
2096 |
|
|
2097 |
|
Fix 2009/09/04 |
2098 |
|
|
2099 |
|
@ Fix wrong ccs_profile() calls. |
2100 |
|
|
2101 |
|
I can't call ccs_profile() for profile existence test because |
2102 |
|
ccs_profile() never returns NULL. |
2103 |
|
|
2104 |
|
Fix 2009/09/06 |
2105 |
|
|
2106 |
|
@ Fix wrong error code in ccs_try_alt_exec(). |
2107 |
|
|
2108 |
|
ccs_try_alt_exec() was returning ENOMEM when kmalloc() failed. |
2109 |
|
It needs to return -ENOMEM to fail. |
2110 |
|
|
2111 |
|
Fix 2009/09/10 |
2112 |
|
|
2113 |
|
@ Do not check umount() permission for mount(MS_MOVE) requests. |
2114 |
|
|
2115 |
|
Until 1.6.x , umount() restriction was black listing. In 1.7.0 , it is |
2116 |
|
white listing. This change caused "mount --move old new" requests to |
2117 |
|
require "allow_unmount old" permission in addition to |
2118 |
|
"allow_mount old new --move 0" permission. |
2119 |
|
But we don't want to allow umount(old) requests when we want to allow |
2120 |
|
only mount(old, new, MS_MOVE) requests. Thus, I modified not to check |
2121 |
|
"allow_unmount old" permission for mount(old, new, MS_MOVE) requests. |
2122 |
|
|
2123 |
|
Fix 2009/09/11 |
2124 |
|
|
2125 |
|
@ Support recursive match operators. |
2126 |
|
|
2127 |
|
Until now, ccs_path_matches_pattern() did not support recursive |
2128 |
|
comparison. Thus, users had to repeat "/\*" when they want to specify |
2129 |
|
recursively. |
2130 |
|
|
2131 |
|
I introduced "\{" and "\}" as repetition operator. |
2132 |
|
To ensure consistency with TOMOYO's '/'-tokenized pattern matching rules |
2133 |
|
and "\-" operator, only "/\{dir\}/" sequences (where dir does not contain |
2134 |
|
'/') is permitted. |
2135 |
|
|
2136 |
|
Fix 2009/09/24 |
2137 |
|
|
2138 |
|
@ Don't check chmod/chown capability for requests from kernel. |
2139 |
|
|
2140 |
|
Until now, ccs_setattr_permission() was inserted in notify_change(). |
2141 |
|
But notify_change() is also called by requests from kernel (e.g. UnionFS) |
2142 |
|
and it made difficult to use TOMOYO on UnionFS. |
2143 |
|
|
2144 |
|
Thus, I moved ccs_capable() checks from ccs_setattr_permission() to |
2145 |
|
ccs_chmod_permission() and ccs_chown_permission(), and removed |
2146 |
|
ccs_setattr_permission(). |
2147 |
|
|
2148 |
|
Fix 2009/09/25 |
2149 |
|
|
2150 |
|
@ Embed more information into audit logs. |
2151 |
|
|
2152 |
|
Until now, /proc/ccs/grant_log /proc/ccs/reject_log /proc/ccs/query were |
2153 |
|
not printing file's information (e.g. file's uid/gid/mode). |
2154 |
|
|
2155 |
|
Recently, users who started using "if" clause expect that the learning |
2156 |
|
mode automatically adds various conditions like "if task.uid=path1.uid". |
2157 |
|
|
2158 |
|
But the profile will become too complicated if I support all possible |
2159 |
|
conditions. Thus, I added all information which is enough to generate |
2160 |
|
"if" clause with all possible conditions from audit logs. |
2161 |
|
|
2162 |
|
Now, the learning mode got different usage. Users can specify |
2163 |
|
"CONFIG::learning={ max_entry=0 }" in the profile. All requests which |
2164 |
|
are not permitted by policy will be sent to /proc/ccs/reject_log with |
2165 |
|
"mode=learning" header lines. Users can selectively append conditions |
2166 |
|
and append to the policy using "/usr/sbin/ccs-loadpolicy -d". |
2167 |
|
The learning mode with "CONFIG::learning={ max_entry=0 }" is almost |
2168 |
|
the same with the permissive mode, only difference is "mode=learning" |
2169 |
|
and "mode=permissive". |
2170 |
|
|
2171 |
|
Fix 2009/10/05 |
2172 |
|
|
2173 |
|
@ Fix size truncation bug at ccs_memcmp(). |
2174 |
|
|
2175 |
|
ccs_memcmp() was using "u8" for size parameter by error. Therefore, when |
2176 |
|
size >= 256 was passed to ccs_memcmp(), it was doing partial comparison |
2177 |
|
(incorrect result) or read overrun (CPU stall). |
2178 |
|
|
2179 |
|
ccs_memcmp() should use "size_t" for size parameter because size of |
2180 |
|
"struct ccs_condition" may exceed 256 bytes if complicated condition was |
2181 |
|
given. |
2182 |
|
|
2183 |
|
Fix 2009/10/08 |
2184 |
|
|
2185 |
|
@ Add CONFIG_CCSECURITY_DEFAULT_LOADER option. |
2186 |
|
|
2187 |
|
I made the default policy loader's pathname ( /sbin/ccs-init ) |
2188 |
|
configurable. |
2189 |
|
|
2190 |
|
@ Add CONFIG_CCSECURITY_ALTERNATIVE_TRIGGER option. |
2191 |
|
|
2192 |
|
Some environments do not have /sbin/init . In such environments, we need |
2193 |
|
to use different program's pathname (e.g. /init or /linuxrc ) as |
2194 |
|
activation trigger. |
2195 |
|
|
2196 |
|
Thus, I made the alternative trigger ( /sbin/ccs-start ) configurable. |
2197 |
|
|
2198 |
|
Fix 2009/11/02 |
2199 |
|
|
2200 |
|
@ Fix buffer contention. |
2201 |
|
|
2202 |
|
A permission like |
2203 |
|
|
2204 |
|
allow_env PATH if exec.envp["PATH"]="/" |
2205 |
|
|
2206 |
|
was not working since I was using the same buffer for both environment |
2207 |
|
variable's name and value. |
2208 |
|
|
2209 |
|
Fix 2009/11/03 |
2210 |
|
|
2211 |
|
@ Fix memory leak in ccs_write_address_group_policy(). |
2212 |
|
|
2213 |
|
I forgot to call kfree() if same entry was added. |
2214 |
|
|
2215 |
|
@ Reduce mutexes. |
2216 |
|
|
2217 |
|
I was using mutex_lock()/mutex_unlock() so that I can use |
2218 |
|
atomic_dec_and_test() for removing an element from a list. |
2219 |
|
I moved that operation to garbage collector in order to reduce frequency |
2220 |
|
of mutex_lock()/mutex_unlock() calls. |
2221 |
|
|
2222 |
|
@ Escape from nested loops correctly. |
2223 |
|
|
2224 |
|
In ccs_read_address_group_policy(), I was escaping from nested loops |
2225 |
|
correctly. But in ccs_read_path_group_policy() and |
2226 |
|
ccs_read_number_group_policy(), I wasn't. |
2227 |
|
|
2228 |
|
As a result, reading path_group and number_group caused kernel oops |
2229 |
|
when they were not read atomically. |
2230 |
|
|
2231 |
|
Fix 2009/11/06 |
2232 |
|
|
2233 |
|
@ Fix incorrect allow_mount audit log. |
2234 |
|
|
2235 |
|
Audit log for allow_mount was using decimal format. |
2236 |
|
It needs to use hexadecimal format. |
2237 |
|
|
2238 |
|
Fix 2009/11/09 |
2239 |
|
|
2240 |
|
@ Add profile version check. |
2241 |
|
|
2242 |
|
To avoid upgrading from TOMOYO 1.6.x to TOMOYO 1.7.x without upgrading |
2243 |
|
/proc/ccs/profile (which results in not protecting the system at all), |
2244 |
|
I added a check for PROFILE_VERSION= . |
2245 |
|
|
2246 |
|
Version 1.7.1 2009/11/11 Fourth anniversary release. |
2247 |
|
|
2248 |
|
Fix 2009/11/13 |
2249 |
|
|
2250 |
|
@ Don't use core_initcall() for initializing lock for GC. |
2251 |
|
|
2252 |
|
Some kernels call TOMOYO's hooks before processing core_initcall(). |
2253 |
|
Thus, I can't use core_initcall() for initializing lock for GC. |
2254 |
|
|
2255 |
|
Fix 2009/11/18 |
2256 |
|
|
2257 |
|
@ Don't check "allow_write" permission for open(O_RDONLY | O_TRUNC). |
2258 |
|
|
2259 |
|
Since TOMOYO checks "allow_truncate" permission rather than "allow_write" |
2260 |
|
permission for O_TRUNC, I need to distinguish open(O_RDONLY | O_TRUNC) |
2261 |
|
and open(O_RDWR | O_TRUNC). But I made a mistake between TOMOYO 1.7.0 and |
2262 |
|
1.7.1 which made it impossible for TOMOYO for kernels 2.6.14 and earlier |
2263 |
|
to distinguish them. |
2264 |
|
|
2265 |
|
Fix 2009/11/27 |
2266 |
|
|
2267 |
|
@ Use newly created domain's name for domain creation audit log. |
2268 |
|
|
2269 |
|
Since 1.7.0 , /proc/ccs/reject_log was by error using existing domain's |
2270 |
|
name when auditing newly created domain's "use_profile" line. |
2271 |
|
|
2272 |
|
Fix 2009/12/12 |
2273 |
|
|
2274 |
|
@ Use rcu_read_lock() for find_task_by_pid(). |
2275 |
|
|
2276 |
|
Since kernel 2.6.18 , caller of find_task_by_pid() needs to call |
2277 |
|
rcu_read_lock() rather than read_lock(&tasklist_lock) because find_pid() |
2278 |
|
uses RCU primitives but spinlock does not prevent RCU callback if |
2279 |
|
preemptive RCU ( CONFIG_PREEMPT_RCU or CONFIG_TREE_PREEMPT_RCU ) is |
2280 |
|
enabled. |
2281 |
|
|
2282 |
|
Fix 2009/12/15 |
2283 |
|
|
2284 |
|
@ Allow deleting "quota_exceeded" and "transition_failed" entries. |
2285 |
|
|
2286 |
|
To notify users of "this domain has too many entries to hold" and "some |
2287 |
|
process in this domain was not able to perform domain transition", |
2288 |
|
"quota_exceeded" and "transition_failed" messages are used respectively. |
2289 |
|
These messages were not deletable. But it is more convenient for users |
2290 |
|
to be notified again if such events occurred again after tuning policy. |
2291 |
|
Thus, I made these messages deletable. |
2292 |
|
|
2293 |
|
Fix 2009/12/17 |
2294 |
|
|
2295 |
|
@ Don't check read permission in ccs_try_alt_exec(). |
2296 |
|
|
2297 |
|
While I was trying to remove ccs_execve_list list for GC optimization |
2298 |
|
between TOMOYO 1.7.0 and 1.7.1 , I made a mistake which made TOMOYO to |
2299 |
|
check allow_read permission of the programs specified by execute_handler |
2300 |
|
and denied_execute_handler keywords. |
2301 |
|
|
2302 |
|
@ Don't check DAC permission if disabled mode. |
2303 |
|
|
2304 |
|
I was checking DAC permissions regarding directory entry modification |
2305 |
|
operations (e.g. mkdir()) even if mode=disabled . It is a waste of CPU |
2306 |
|
resource to check DAC permissions when MAC permissions are not checked. |
2307 |
|
Thus, I modified to skip DAC permission checks if mode=disabled . |
2308 |
|
|
2309 |
|
Fix 2009/12/19 |
2310 |
|
|
2311 |
|
@ Fix memory leak in ccs_environ(). |
2312 |
|
|
2313 |
|
When I fixed a bug that a permission like |
2314 |
|
|
2315 |
|
allow_env PATH if exec.envp["PATH"]="/" |
2316 |
|
|
2317 |
|
was not working (2009/11/02), I allocated two buffers but only one buffer |
2318 |
|
was released. |
2319 |
|
|
2320 |
|
This bug will trigger OOM killer if environment variable checking is |
2321 |
|
enabled. |
2322 |
|
|
2323 |
|
Fix 2010/01/17 |
2324 |
|
|
2325 |
|
@ Use current domain's name for execute_handler audit log. |
2326 |
|
|
2327 |
|
Since 1.6.7 , /proc/ccs/grant_log was by error using next domain's name |
2328 |
|
when auditing current domain's "execute_handler" line. |
2329 |
|
|
2330 |
|
Fix 2010/03/02 |
2331 |
|
|
2332 |
|
@ Allow domain transition without execve(). |
2333 |
|
|
2334 |
|
To be able to split permissions for Apache's CGI programs which are |
2335 |
|
executed without execve(), I added special domain transition which is |
2336 |
|
performed by atomically writing '\0'-terminated binary string to |
2337 |
|
/proc/ccs/.transition interface. For example, a process which belongs to |
2338 |
|
"<kernel> /usr/sbin/httpd" domain will transit to |
2339 |
|
"<kernel> /usr/sbin/httpd //app=cgi1\040id=10000" domain by atomically |
2340 |
|
writing "app=cgi1 id=10000" + '\0' to /proc/ccs/.transition using |
2341 |
|
Apache's ap_hook_handler() functionality. |
2342 |
|
|
2343 |
|
Note that '\0'-terminated binary string is converted to TOMOYO's string |
2344 |
|
inside kernel and prefix "//" is automatically added to the string so |
2345 |
|
that domainname does not conflict with domainnames created by execve(). |
2346 |
|
Without this prefix, if "<kernel> /usr/sbin/sshd /bin/bash" domain is |
2347 |
|
allowed to open /proc/ccs/.transition for writing and |
2348 |
|
"<kernel> /usr/sbin/sshd /bin/bash /usr/bin/passwd" domain is allowed to |
2349 |
|
access /etc/shadow , /bin/bash will be able to access /etc/shadow by |
2350 |
|
atomically writing "/usr/bin/passwd" + '\0' to /proc/ccs/.transition . |
2351 |
|
Allowing /bin/bash to access /etc/shadow is not what people want. |
2352 |
|
|
2353 |
|
Permission for this operation is checked by "allow_transit" keyword. |
2354 |
|
Unlike "allow_execute" keyword, the string parameter for "allow_transit" |
2355 |
|
keyword does not refer a real file on filesystem's namespace. Therefore, |
2356 |
|
you can store any combination of parameters like LDAP's DN entry in the |
2357 |
|
string parameter for "allow_transit" keyword. |
2358 |
|
|
2359 |
|
Fix 2010/03/08 |
2360 |
|
|
2361 |
|
@ Allow building as loadable kernel module. |
2362 |
|
|
2363 |
|
To be able to minimize filesize increment of vmlinux, I made it |
2364 |
|
possible to compile TOMOYO Linux as loadable kernel module. |
2365 |
|
Although patching the kernel source and recompiling the kernel are |
2366 |
|
inevitable, this change will make it easier to enable TOMOYO Linux |
2367 |
|
when there is a filesize limitation on vmlinux (e.g. embedded systems). |
2368 |
|
|
2369 |
|
Fix 2010/03/25 |
2370 |
|
|
2371 |
|
@ Fix ccs_get_ipv6_address() bug. |
2372 |
|
|
2373 |
|
Since 1.7.0 , ccs_get_ipv6_address() was by error returning address of |
2374 |
|
"struct list_head ccs_address_list" if memory allocation failed. |
2375 |
|
As a result, ccs_put_ipv6_address() will modify memory near |
2376 |
|
"struct list_head ccs_address_list" if memory allocation failed. |
2377 |
|
|
2378 |
|
Fix 2010/03/26 |
2379 |
|
|
2380 |
|
@ Fix ccs_lport_reserved() bug. |
2381 |
|
|
2382 |
|
Since 1.7.0 , ccs_lport_reserved() was by error checking wrong port |
2383 |
|
number. As a result, "deny_autobind" keyword was not working as expected. |
2384 |
|
|
2385 |
|
Version 1.7.2 2010/04/01 Feature enhancement release. |
2386 |
|
|
2387 |
|
Fix 2010/04/10 |
2388 |
|
|
2389 |
|
@ Fix invalid "struct nameidata" to "struct path" conversion macro. |
2390 |
|
|
2391 |
|
Regarding kernels 2.6.24 and earlier, I was converting "struct nameidata" |
2392 |
|
to "struct path" in caller side so that I can unify the callee function's |
2393 |
|
parameter type. But it turned out that the macro I used did not follow C |
2394 |
|
standards and did not work with gcc 4.x . As a result, "allow_pivot_root" |
2395 |
|
keyword was not working as expected. |
2396 |
|
|
2397 |
|
Fix 2010/05/05 |
2398 |
|
|
2399 |
|
@ Fix incorrect audit on/off control. |
2400 |
|
|
2401 |
|
The grant_log= and reject_log= parameters of CONFIG::misc::env were not |
2402 |
|
used because I forgot to update request type. As a result, those of |
2403 |
|
CONFIG::file::execute were used for CONFIG::misc::env . |
2404 |
|
|
2405 |
|
Those of CONFIG::file::rewrite were not used because I forgot to update |
2406 |
|
request type. As a result, those of CONFIG::file::truncate were used for |
2407 |
|
CONFIG::file::rewrite . |
2408 |
|
|
2409 |
|
Fix 2010/05/10 |
2410 |
|
|
2411 |
|
@ Fix incorrect out of memory warning. |
2412 |
|
|
2413 |
|
Out of memory warnings were not printed in some cases by error. |
2414 |
|
|
2415 |
|
Fix 2010/05/27 |
2416 |
|
|
2417 |
|
@ Add missing rcu_dereference() for ccs_find_execute_handler(). |
2418 |
|
|
2419 |
|
Since 1.7.0 , ccs_find_execute_handler() was by error using |
2420 |
|
list_for_each_entry() rather than list_for_each_entry_rcu(). |
2421 |
|
This bug affects only Alpha architecture. |
2422 |
|
|
2423 |
|
Fix 2010/06/03 |
2424 |
|
|
2425 |
|
@ Fix missing sanity check for "file_pattern". |
2426 |
|
|
2427 |
|
Since 1.7.0 , ccs_write_pattern_policy() was by error accepting |
2428 |
|
invalid pathname. |
2429 |
|
|
2430 |
|
Fix 2010/06/09 |
2431 |
|
|
2432 |
|
@ Add missing ccs_put_name() in ccs_parse_envp(). |
2433 |
|
|
2434 |
|
Since 1.7.0 , ccs_parse_envp() was not calling ccs_put_name() if |
2435 |
|
environment variable's value ('if exec.envp["name"]="value"' condition) |
2436 |
|
was invalid. |
2437 |
|
|
2438 |
|
@ Add missing NULL check in ccs_condition(). |
2439 |
|
|
2440 |
|
Since 1.7.0 , if 'if symlink.target=' part was given against non-file |
2441 |
|
permissions (e.g. allow_env PATH if symlink.target="/"), it triggered |
2442 |
|
NULL pointer dereference. |
2443 |
|
|
2444 |
|
Fix 2010/07/29 |
2445 |
|
|
2446 |
|
@ Change keyword syntax. |
2447 |
|
|
2448 |
|
I removed "allow_" prefix from directives. New directives for files are |
2449 |
|
prefixed with "file ". For example, "allow_read" changed to "file read", |
2450 |
|
"allow_ioctl" changed to "file ioctl". New directive for "allow_network" |
2451 |
|
is "network". New directive for "allow_env" is "misc env". New directive |
2452 |
|
for "allow_signal" is "ipc signal". New directive for "allow_capability" |
2453 |
|
is "capability". These directives correspond with keywords used by |
2454 |
|
profile's CONFIG lines. |
2455 |
|
|
2456 |
|
I removed "deny_rewrite" and "allow_rewrite" directives and introduced |
2457 |
|
"file append" directive. Thus, permission for open(O_WRONLY | O_APPEND) |
2458 |
|
changed from "allow_write" + "allow_rewrite" to "file append". |
2459 |
|
|
2460 |
|
I removed "SYS_MOUNT", "SYS_UMOUNT", "SYS_CHROOT", "SYS_KILL", |
2461 |
|
"SYS_LINK", "SYS_SYMLINK", "SYS_RENAME", "SYS_UNLINK", "SYS_CHMOD", |
2462 |
|
"SYS_CHOWN", "SYS_IOCTL", "SYS_PIVOT_ROOT" keywords from capabilities |
2463 |
|
because these permissions can be checked by other directives (e.g. |
2464 |
|
"file mount", "ipc signal"). |
2465 |
|
|
2466 |
|
I also removed "conceal_mount" keyword from capabilities because this |
2467 |
|
check requires hooks in filesystem part while almost all hooks for |
2468 |
|
filesystem part have moved to LSM by Linux 2.6.34. |
2469 |
|
|
2470 |
|
@ Distinguish send() and recv() operations for UDP and IP protocols. |
2471 |
|
|
2472 |
|
Until now, it was impossible for UDP and IP protocols to allow either |
2473 |
|
only sending or only receiving because permissions were aggregated with |
2474 |
|
"connect" keyword. I broke "connect" keyword into "send" and "recv" |
2475 |
|
keywords so that you can keep access control for send() operation enabled |
2476 |
|
when you have to turn access control for recv() operation off due to |
2477 |
|
application breakage by filtering incoming datagram. |
2478 |
|
|
2479 |
|
@ Wait for next connection/datagram if current connection/datagram was |
2480 |
|
discarded. |
2481 |
|
|
2482 |
|
Regarding "network TCP accept", "network UDP recv", "network RAW recv" |
2483 |
|
keywords, I modified to wait for next connection/datagram if current |
2484 |
|
connection/datagram was discarded. LSM hooks for these keywords are |
2485 |
|
currently missing because this behavior may break applications. |
2486 |
|
If you found applications broken by this behavior, you can set |
2487 |
|
CONFIG::network::inet_tcp_accept and/or CONFIG::network::inet_udp_recv |
2488 |
|
and/or CONFIG::network::inet_raw_recv to mode=disabled in order to |
2489 |
|
disable filtering for incoming connection/datagram. |
2490 |
|
|
2491 |
|
@ Allow specifying multiple permissions in a line. |
2492 |
|
|
2493 |
|
Until now, only "allow_read/write" can be specified for combination of |
2494 |
|
"allow_read" + "allow_write". Now, you can combine other permissions as |
2495 |
|
long as type of parameters for these permissions is same. For example, |
2496 |
|
"file read/write/append/execute/unlink/truncate /tmp/file" is correct |
2497 |
|
but "file read/write/create /tmp/file" is wrong because "file create" |
2498 |
|
requires create mode whereas "file read" and "file write" do not. |
2499 |
|
|
2500 |
|
@ Allow wildcard for execute permission and domainname. |
2501 |
|
|
2502 |
|
Until now, to execute programs with temporary names, "aggregator" is |
2503 |
|
needed. To simplify code, I modified to accept wildcards for execute |
2504 |
|
permission and domainname. Now, you can directly specify |
2505 |
|
"file execute /tmp/logrotate.\?\?\?\?\?\?" and use |
2506 |
|
"/tmp/logrotate.\?\?\?\?\?\?" within domainnames. |
2507 |
|
|
2508 |
|
@ Change pathname for non-rename()able filesystems. |
2509 |
|
|
2510 |
|
LSM version of TOMOYO wants to use /proc/self/ rather than /proc/$PID/ if |
2511 |
|
$PID matches current thread's process ID in order to prevent current |
2512 |
|
thread from accessing other process's information unless needed. |
2513 |
|
But since procfs can be mounted on various locations (e.g. /proc/ /proc2/ |
2514 |
|
/p/ /tmp/foo/100/p/ ), LSM version of TOMOYO cannot tell that whether the |
2515 |
|
numeric part in the string returned by __d_path() represents process ID |
2516 |
|
or not. |
2517 |
|
|
2518 |
|
Therefore, to be able to convert from $PID to self no matter where procfs |
2519 |
|
is mounted, I changed pathname representations for filesystems which do |
2520 |
|
not support rename() operation (e.g. proc, sysfs, securityfs). |
2521 |
|
|
2522 |
|
Now, "/proc/self/mounts" changed to "proc:/self/mounts" and |
2523 |
|
"/sys/kernel/security/" changed to "sys:/kernel/security/" and |
2524 |
|
"/dev/pts/0" changed to "devpts:/0". |
2525 |
|
|
2526 |
|
@ Add a new keyword "any" for domain transition control. |
2527 |
|
|
2528 |
|
To be able to make it easier to apply execute_handler on each domain, |
2529 |
|
I added "any" keyword to domain transition control keywords. Now, |
2530 |
|
"initialize_domain /usr/sbin/sshd" changed to |
2531 |
|
"initialize_domain /usr/sbin/sshd from any" and |
2532 |
|
"keep_domain <kernel> /usr/sbin/sshd /bin/bash" changed to |
2533 |
|
"keep_domain any from <kernel> /usr/sbin/sshd /bin/bash". |
2534 |
|
|
2535 |
|
"keep_domain /path/to/execute_handler from any" will allow you to apply |
2536 |
|
execute_handler for any domains without creating domains for |
2537 |
|
execute_handler. |
2538 |
|
|
2539 |
|
@ Change buffering mode for reading policy. |
2540 |
|
|
2541 |
|
To be able to read() very very long lines correctly, I changed the way |
2542 |
|
TOMOYO buffers policy for reading. |
2543 |
|
|
2544 |
|
@ Introduce "acl_group" keyword. |
2545 |
|
|
2546 |
|
Until now, it was possible to specify only "allow_read" and "allow_env" |
2547 |
|
keywords in the exception policy. |
2548 |
|
|
2549 |
|
Since some operations like "file read/write/append /dev/null" and |
2550 |
|
"network UDP send/recv @DNS_SERVER 53" are very common and should be |
2551 |
|
permitted to all domains, I introduced "acl_group" keyword for giving |
2552 |
|
such permissions. |
2553 |
|
|
2554 |
|
For example, specify "acl_group 0 file read/write/append /dev/null" in |
2555 |
|
the exception policy and specify "use_group 0" from the domains in the |
2556 |
|
domain policy. |
2557 |
|
|
2558 |
|
"ignore_global_allow_read" and "ignore_global_allow_env" keywords were |
2559 |
|
removed from domain policy and "use_group" keyword was added. |
2560 |
|
|
2561 |
|
@ Allow controlling generation of access granted logs for per an entry |
2562 |
|
basis. |
2563 |
|
|
2564 |
|
I added per-entry flag which controls generation of grant logs because |
2565 |
|
Xen and KVM issues ioctl requests so frequently. For example, |
2566 |
|
|
2567 |
|
file ioctl /dev/null 0x5401 ; set audit=no |
2568 |
|
|
2569 |
|
will suppress /proc/ccs/grant_log even if profile says grant_log=yes . |
2570 |
|
|
2571 |
|
file ioctl /dev/null 0x5401 ; set audit=yes |
2572 |
|
|
2573 |
|
will generate /proc/ccs/grant_log even if profile says grant_log=no . |
2574 |
|
|
2575 |
|
file ioctl /dev/null 0x5401 |
2576 |
|
|
2577 |
|
will generate /proc/ccs/grant_log only if profile says grant_log=yes . |
2578 |
|
|
2579 |
|
This flag is intended for frequently accessed resources like |
2580 |
|
|
2581 |
|
file read /var/www/html/\{\*\}/\*.html ; set audit=no |
2582 |
|
|
2583 |
|
. |
2584 |
|
|
2585 |
|
@ Optimize for object's size. |
2586 |
|
|
2587 |
|
I merged similar code in order to reduce object's filesize. |