--- trunk/1.7.x/ccs-patch/README.ccs 2009/09/06 02:18:23 2998 +++ trunk/1.7.x/ccs-patch/README.ccs 2009/11/03 03:51:07 3131 @@ -193,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. @@ -404,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. @@ -428,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" @@ -444,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. @@ -492,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 @@ -758,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 @@ -1984,7 +1984,7 @@ overrun when slob allocator is used, for slob allocator allocates exactly 4000 bytes whereas slab and slub allocators allocate 4096 bytes. -Fix 2008/09/01 +Fix 2009/09/01 @ Add garbage collector support. @@ -2085,25 +2085,136 @@ Thus, I added global PID in audit logs. - @ Transit to new domain before do_execve() suceeds. + @ 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 2008/09/03 Feature enhancement release. +Version 1.7.0 2009/09/03 Feature enhancement release. -Fix 2008/09/04 +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 2008/09/06 +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.