--- trunk/1.6.x/ccs-patch/README.ccs 2008/04/20 05:26:45 1117 +++ trunk/1.6.x/ccs-patch/README.ccs 2008/08/21 06:59:21 1471 @@ -1146,11 +1146,11 @@ Fix 2008/02/05 - @ Use find_task_by_vpid() instead of find_task_pid(). + @ Use find_task_by_vpid() instead of find_task_by_pid(). Kernel 2.6.24 introduced PID namespace. To search PID given from userland, the kernel needs to use - find_task_by_vpid() instead of find_task_pid(). + find_task_by_vpid() instead of find_task_by_pid(). Fix 2008/02/14 @@ -1384,3 +1384,162 @@ Turbolinux 10 Server's 2.6.8 kernel backported kzalloc() as an inlined function, resulting compilation error at kzalloc(). I converted kzalloc() from an inlined function into a macro. + +Fix 2008/04/21 + + @ Add workaround for gcc 3.2.2's inline bug. + + RedHat Linux 9's gcc 3.2.2 generated a bad code + if ((var_of_u8 & 0x000000BF) & 0x80000000) { } + where the expected code is + if ((var_of_u8 & 0xBF) & 0x80) { } + when embedding ccs_acl_type2() into print_entry(), + resulting runtime BUG(). + I added the expected code explicitly as a workaround. + +Fix 2008/05/06 + + @ Add memory quota. + + 1.5.x returns -ENOMEM when FindNextDomain() failed to create a new + domain, but I forgot to return -ENOMEM when find_next_domain() failed to + create a new domain. + + A domain is automatically created by find_next_domain() only if + the domain for the requested program doesn't exist. + This behavior is for the administrator's convenience. + The administrator needn't to know how many domains are needed for running + the whole programs in the system beforehand when developing the policy. + But the administrator does not want the kernel to reject execution of the + requested program when developing the policy. + + So, I think it is better to grant execution of programs even if + find_next_domain() failed to create a new domain than reject execution. + Thus, I decided not to return -ENOMEM when find_next_domain() failed to + create a new domain. This exception breaks the domain transition rules, + so I print "transition_failed" warning in /proc/ccs/domain_policy + when this exception happened. + + Also, to prevent the system from being halted by unexpectedly allocating + all kernel memory for the policy, I added memory quota. + This quota is configurable via /proc/ccs/meminfo like + + echo Shared: 1048576 > /proc/ccs/meminfo + echo Private: 1048576 > /proc/ccs/meminfo + +Version 1.6.1 2008/05/10 Bug fix release. + +Fix 2008/06/04 + + @ Check open mode of /proc/ccs/ interface. + + It turned out that I can avoid allocating memory for reading if + FMODE_READ is not set and memory for writing if FMODE_WRITE is not set. + + @ Wait for completion of /sbin/ccs-init . + + Since 2.4 kernel's call_usermodehelper() can't wait for termination of + the executed program, I was using the close() request of + /proc/ccs/meminfo to indicate that loading policy has finished. + But since /proc/ccs/meminfo could be accessed for setting memory quota + by /etc/ccs/ccs-post-init , I stopped using the close() request. + The policy loader no longer need to access /proc/ccs/meminfo to notify + the kernel that loading policy has finished. + +Fix 2008/06/05 + + @ Fix realpath for pipes and sockets. + + Kernel 2.6.22 and later use different method for calculating d_path(). + Since fs/realpath.c didn't notice the change, the realpath of pipes + appeared as "pipe:" rather than "pipe:[\$]" when they are opened via + /proc/PID/fd/ directory. + + @ Add process's information into /proc/ccs/query . + + While /proc/ccs/grant_log and /proc/ccs/reject_log contain process's + information, /proc/ccs/query doesn't contain it. + To be able to utilize ccs-queryd and ccs-notifyd more, I added it into + /proc/ccs/query . + +Fix 2008/06/10 + + @ Allow using patterns for globally readable files. + + To allow users specify locale specific files to globally readable files, + I relaxed checking in update_globally_readable_entry(). + +Fix 2008/06/11 + + @ Remove ALLOW_ENFORCE_GRACE parameter. + + Since unexpected requests caused by doing software updates can happen + in all profiles, users likely have to write ALLOW_ENFORCE_GRACE=enabled + to all profiles. And it makes meaningless to allow users to selectively + enable specific profile's ALLOW_ENFORCE_GRACE parameter. + So, I removed ALLOW_ENFORCE_GRACE parameter. + Now, the system behaves as if ALLOW_ENFORCE_GRACE=enabled is specified. + The behavior of "delayed enforcing" mode is defined in the following + order. + + (1) The requests are rejected immediately if nobody is opening + /proc/ccs/query interface. + (2) The requests will be rejected in 10 seconds if somebody other than + ccs-queryd (such as less(1)) is opening /proc/ccs/query interface, + for such process doesn't write dummy decisions. + +Fix 2008/06/22 + + @ Pass escaped pathname to audit_execute_handler_log(). + + I was passing unescaped pathname to audit_execute_handler_log() + which causes /proc/ccs/grant_log contain whitespace characters + if execute handler's pathname contains whitespace characters. + +Fix 2008/06/25 + + @ Return 0 when ccs_may_umount() succeeds. + + I forgot to clear error value in ccs_may_umount() when the requested + directory didn't match "deny_unmount" keyword. As a result, any umount() + request with RESTRICT_UNMOUNT=enforcing returned -EPERM error. + +Version 1.6.2 2008/06/25 Usability enhancement release. + +Fix 2008/07/01 + + @ Fix "Compilation failure" with 2.4.20 kernel. + + RedHat Linux 9's 2.4.20 kernel backported O(1) scheduler patch, + resulting compilation error at ccs_load_policy(). + I added defined(TASK_DEAD) check. + +Fix 2008/07/08 + + @ Don't check permissions if vfsmount is NULL. + + Some filesystems (e.g. unionfs) pass NULL vfsmount. + I changed fs/tomoyo_file.c not to try to calculate pathnames + if vfsmount is NULL. + +Version 1.6.3 2008/07/15 Bug fix release. + +Fix 2008/08/21 + + @ Add workaround for gcc 4.3's bug. + + In some environments, fs/tomoyo_network.c could not be compiled + because of gcc 4.3's bug. + I modified save_ipv6_address() to use "integer literal" value + instead for "static const u8" variable. + + @ Change prototypes of some functions. + + To support 2.6.27 kernels, I replaced "struct nameidata" with + "struct path" for some functions. + + @ Detect distributor specific patches automatically. + + Since kernels with AppArmor patch applied is increasing, + I introduced a mechanism which determines whether specific patches + are applied or not, based on "#define" directives in the patches.