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 |
|
|
1918 |
|
|
1919 |
This problem happens on little endian platforms (e.g. x86). |
This problem happens on little endian platforms (e.g. x86). |
1920 |
|
|
|
Fix 2009/04/20 |
|
|
|
|
|
@ Update recvmsg() hooks. |
|
|
|
|
|
Since 1.5.0, I was doing network access control for incoming UDP and RAW |
|
|
packets inside skb_recv_datagram(). But to synchronize with LSM version, |
|
|
I moved ccs_recv_datagram_permission() hook from skb_recv_datagram() to |
|
|
udp_recvmsg()/udpv6_recvmsg()/raw_recvmsg()/rawv6_recvmsg() with name |
|
|
change to ccs_recvmsg_permission(). |
|
|
|
|
1921 |
Fix 2009/05/08 |
Fix 2009/05/08 |
1922 |
|
|
1923 |
@ Add condition for symlink's target pathname. |
@ Add condition for symlink's target pathname. |
1963 |
|
|
1964 |
I modified to unlock the mutex before calling get_fs_type(). |
I modified to unlock the mutex before calling get_fs_type(). |
1965 |
|
|
1966 |
Version 1.6.8 2009/05/?? Feature enhancement release. |
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 2008/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 ruduce use of spinlocks. |
2050 |
|
|
2051 |
|
@ Rewrite ccs-patch-2.\*.diff . |
2052 |
|
|
2053 |
|
ccs-patch-2.\*.diff was rewriteen 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() suceeds. |
2089 |
|
|
2090 |
|
Permission checks for interpreters and environment variables are |
2091 |
|
done using new domain. In order to be 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 2008/09/03 Feature enhancement release. |
2096 |
|
|
2097 |
|
Fix 2008/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 2008/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 2008/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. |