--- trunk/1.6.x/ccs-patch/README.ccs 2009/05/19 01:11:55 2562 +++ trunk/1.7.x/ccs-patch/README.ccs 2009/11/03 03:51:07 3131 @@ -16,10 +16,6 @@ This project was very inspired by the comic "Card Captor SAKURA", one of the CLAMP's masterworks. -The names SAKURA and TOMOYO and SYAORAN were borrowed from the comic -with the heartfelt thanks to CLAMP. - - ChangeLog: @@ -197,7 +193,7 @@ @ Fix handling of trailing '\*' in PathMatchesToPattern(). PathMatchesToPattern("/tmp/", "/tmp/\*") returned true - because "\*" matches to "more than or equals to 0 character + because "\*" matches "zero or more repetitions of characters until '/' or end". But since this is a comparison between directory and non-directory, this should not match. @@ -408,14 +404,14 @@ @ Change behavior of pathname pattern matching. - Until now, it was impossible to use patterns like "\*.txt" - because "\*" matched to more than 0 characters until next '/'. - Now, "\*" matches to more than 0 characters. + Until now, it was impossible to use patterns like "\*.txt" because + "\*" matched zero or more repetitions of characters until next '/'. + Now, "\*" matches zero or more repetitions of characters. Until now, it was impossible to use patterns like "\$00" - because "\$" matched to more than 1 digits until next + because "\$" matched one or more repetitions of digits until next non digit character. - Now, "\$" matches to more than 1 digits. + Now, "\$" matches one or more repetitions of digits. Also, new patterns "\x" "\X" "\a" "\A" "\@" are added. @@ -432,7 +428,7 @@ @ Change matching rule for CheckFileACL(). - Until now, only first entry that matched to the requested pathname + Until now, only first entry that matched the requested pathname was used for permission checking. For example, two entries "2 /tmp/file-\$.txt" @@ -448,7 +444,7 @@ This may potentially cause trouble because the result of permission checks depends on the order of entries. - Now, all entries that matched to the requested pathname + Now, all entries that matched the requested pathname are used for permission checking so that the result of permission checks doesn't depend on the order of entries. @@ -496,7 +492,7 @@ "6 /home/\*/\* if task.uid=path1.uid" allows the domain to read-write user's home directory - only when the file's owner matches to the process's uid. + only when the file's owner matches the process's uid. Fix 2006/08/22 @@ -762,7 +758,7 @@ if /some/program is called from "some_domain" domain. "some_domain" can be just the last component of domainname. - For example, giving "/bin/mail" as "some_domain" matches to + For example, giving "/bin/mail" as "some_domain" matches all domains whose domainname ends with "/bin/mail". Fix 2007/01/19 @@ -1922,16 +1918,6 @@ This problem happens on little endian platforms (e.g. x86). -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(). - Fix 2009/05/08 @ Add condition for symlink's target pathname. @@ -1977,4 +1963,258 @@ I modified to unlock the mutex before calling get_fs_type(). -Version 1.6.8 2009/05/?? Feature enhancement release. +Fix 2009/05/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(). + +Version 1.6.8 2009/05/28 Feature enhancement release. + +Fix 2009/07/03 + + @ Fix buffer overrun when used with CONFIG_SLOB=y . + + Since 1.6.7 , ccs_allocate_execve_entry() was requesting for only 4000 + bytes while the comment says it is 4096 bytes. This may lead to buffer + overrun when slob allocator is used, for slob allocator allocates exactly + 4000 bytes whereas slab and slub allocators allocate 4096 bytes. + +Fix 2009/09/01 + + @ Add garbage collector support. + + Until now, it was impossible to release memory used by deleted policy. + I added SRCU based garbage collector so that memory used by deleted + policy will be automatically released. + + @ Remove word length limitation and line length limitation. + + Until now, the max length of a word is 4000 and the max length of a line + is 8192. To be able to handle longer pathnames, I removed these + limitations. Now, the max length (except the domainname and + argv[]/envp[]) is 128K (which is the max amount of memory kmalloc() + can allocate in most environments). + + @ Support more fine grained profile configuration. + + Profile was reconstructed. + + @ Support more fine grained parameters restrictions. + + "allow_create", "allow_mkdir", "allow_mkfifo", "allow_mksock" check + create mode. "allow_mkblock" and "allow_mkchar" check create mode and + major/minor device numbers. "allow_chmod" check new mode. "allow_chown" + checks new owner. "allow_chgrp" checks new group. + + @ Allow number grouping. + + To help specifying numeric values, a new directive "number_group" is + introduced. + + @ Remove "alias" directive and "allow_argv0" directive. + + Until now, "allow_execute" used dereferenced pathname if it is a symlink + unless explicitly specified by "alias" directive. + + Now, "allow_execute" uses symlink's pathname if it is a symlink. + "exec.realpath" in "if" clause checks the dereferenced pathname. + "exec.argv[0]" in "if" clause checks the invocation name. + + @ Remove /proc/ccs/system_policy and /etc/ccs/system_policy.conf . + + "deny_autobind" was moved to /proc/ccs/exception_policy and + /etc/ccs/exception_policy.conf . Other directives were moved to + /proc/ccs/domain_policy and /etc/ccs/domain_policy.conf . + + @ Remove syaoran filesystem. + + Since "allow_create"/"allow_mkdir"/"allow_mkfifo"/"allow_mksock"/ + "allow_mkblock"/"allow_mkchar"/"allow_chmod"/"allow_chown"/"allow_chgrp" + can restrict mode changes and owner/group changes, there is no need to + restrict these changes at filesystem level. + + Thus, I removed syaoran filesystem. + + @ Reduce spinlocks. + + Until now, TOMOYO was using own list for detecting memory leak. But as + kernel 2.6.31 introduced memory leak detection mechanism + ( CONFIG_DEBUG_KMEMLEAK ), TOMOYO no longer needs to use own list. + + I removed the list to ruduce use of spinlocks. + + @ Rewrite ccs-patch-2.\*.diff . + + ccs-patch-2.\*.diff was rewriteen like LSM hooks. + + @ Don't check "allow_read/write" for open-for-ioctl-only. + + open(pathname, 3) means open for ioctl() only. + Until now, TOMOYO was checking "allow_read/write" for open(pathname, 3). + But since TOMOYO checks "allow_ioctl" for ioctl(), I modified not to + require "allow_read/write" for open(pathname, 3). + + @ Add missing sigqueue() and tgsigqueue() hooks. + + Until now, kill(), tkill(), tgkill() had hooks but sigqueue() and + tgsigqueue() didn't. + + @ Move files from fs/ to security/ccsecurity. + + Config menu section changed from "File systems" to "Security options". + + Kernel config symbols changed from CONFIG_SAKURA CONFIG_TOMOYO + CONFIG_SYAORAN to CONFIG_CCSECURITY . + + @ Add global PID to audit logs. + + ccs-queryd was using domainname for reaching the domain which the process + belongs to, but the domain could be deleted while ccs-queryd is handling + policy violation. If the domain is deleted, ccs-queryd no longer can + reach the domain by domainname. Thus, ccs-queryd now uses PID for + reaching the domain which the process belongs to. + + Kernel 2.6.24 introduced PID namespace. The PID in access logs generated + by a process inside a container is useless for ccs-queryd for reaching + the domain which the process belongs to. + + Thus, I added global PID in audit logs. + + @ Transit to new domain before do_execve() succeeds. + + Permission checks for interpreters and environment variables are + done using new domain. In order to be allow ccs-queryd to reach the new + domain via global PID, I reverted "Don't transit to new domain until + do_execve() succeeds." made on 2008/10/07. + +Version 1.7.0 2009/09/03 Feature enhancement release. + +Fix 2009/09/04 + + @ Fix wrong ccs_profile() calls. + + I can't call ccs_profile() for profile existence test because + ccs_profile() never returns NULL. + +Fix 2009/09/06 + + @ Fix wrong error code in ccs_try_alt_exec(). + + ccs_try_alt_exec() was returning ENOMEM when kmalloc() failed. + It needs to return -ENOMEM to fail. + +Fix 2009/09/10 + + @ Do not check umount() permission for mount(MS_MOVE) requests. + + Until 1.6.x , umount() restriction was black listing. In 1.7.0 , it is + white listing. This change caused "mount --move old new" requests to + require "allow_unmount old" permission in addition to + "allow_mount old new --move 0" permission. + But we don't want to allow umount(old) requests when we want to allow + only mount(old, new, MS_MOVE) requests. Thus, I modified not to check + "allow_unmount old" permission for mount(old, new, MS_MOVE) requests. + +Fix 2009/09/11 + + @ Support recursive match operators. + + Until now, ccs_path_matches_pattern() did not support recursive + comparison. Thus, users had to repeat "/\*" when they want to specify + recursively. + + I introduced "\{" and "\}" as repetition operator. + To ensure consistency with TOMOYO's '/'-tokenized pattern matching rules + and "\-" operator, only "/\{dir\}/" sequences (where dir does not contain + '/') is permitted. + +Fix 2009/09/24 + + @ Don't check chmod/chown capability for requests from kernel. + + Until now, ccs_setattr_permission() was inserted in notify_change(). + But notify_change() is also called by requests from kernel (e.g. UnionFS) + and it made difficult to use TOMOYO on UnionFS. + + Thus, I moved ccs_capable() checks from ccs_setattr_permission() to + ccs_chmod_permission() and ccs_chown_permission(), and removed + ccs_setattr_permission(). + +Fix 2009/09/25 + + @ Embed more information into audit logs. + + Until now, /proc/ccs/grant_log /proc/ccs/reject_log /proc/ccs/query were + not printing file's information (e.g. file's uid/gid/mode). + + Recently, users who started using "if" clause expect that the learning + mode automatically adds various conditions like "if task.uid=path1.uid". + + But the profile will become too complicated if I support all possible + conditions. Thus, I added all information which is enough to generate + "if" clause with all possible conditions from audit logs. + + Now, the learning mode got different usage. Users can specify + "CONFIG::learning={ max_entry=0 }" in the profile. All requests which + are not permitted by policy will be sent to /proc/ccs/reject_log with + "mode=learning" header lines. Users can selectively append conditions + and append to the policy using "/usr/sbin/ccs-loadpolicy -d". + The learning mode with "CONFIG::learning={ max_entry=0 }" is almost + the same with the permissive mode, only difference is "mode=learning" + and "mode=permissive". + +Fix 2009/10/05 + + @ Fix size truncation bug at ccs_memcmp(). + + ccs_memcmp() was using "u8" for size parameter by error. Therefore, when + size >= 256 was passed to ccs_memcmp(), it was doing partial comarison + (incorrect result) or read overrun (CPU stall). + + ccs_memcmp() should use "size_t" for size parameter because size of + "struct ccs_condition" may exceed 256 bytes if complicated condition was + given. + +Fix 2009/10/08 + + @ Add CONFIG_CCSECURITY_DEFAULT_LOADER option. + + I made the default policy loader's pathname ( /sbin/ccs-init ) + configurable. + + @ Add CONFIG_CCSECURITY_ALTERNATIVE_TRIGGER option. + + Some environments do not have /sbin/init . In such environments, we need + to use different program's pathname (e.g. /init or /linuxrc ) as + activation trigger. + + Thus, I made the alternative trigger ( /sbin/ccs-start ) configurable. + +Fix 2009/11/02 + + @ Fix buffer contention. + + A permission like + + allow_env PATH if exec.envp["PATH"]="/" + + was not working since I was using the same buffer for both environment + variable's name and value. + +Fix 2009/11/03 + + @ Fix memory leak in ccs_write_address_group_policy(). + + I forgot to call kfree() if same entry was added. + + @ Reduce mutexes. + + I was using mutex_lock()/mutex_unlock() so that I can use + atomic_dec_and_test() for removing an element from a list. + I moved that operation to garbage collector in order to reduce frequency + of mutex_lock()/mutex_unlock() calls.