--- trunk/1.6.x/ccs-patch/README.ccs 2009/02/17 04:37:03 2178 +++ trunk/1.7.x/ccs-patch/README.ccs 2009/09/01 05:34:46 2975 @@ -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: @@ -1804,10 +1800,6 @@ As remove_arg_zero() uses kmap_atomic(KM_USER0), I modified to use kmap_atomic(KM_USER0) rather than kmap(). - @ Relocate definitions and functions. - - To reduce exposed symbols, I relocated some definitions and functions. - Fix 2009/01/28 @ Fix "allow_read" + "allow_write" != "allow_read/write" problem. @@ -1820,3 +1812,284 @@ Workaround is to write an entry twice when newly appending that entry. If written twice, internal "allow_read" and "allow_write" entries are updated. + +Fix 2009/02/26 + + @ Fix profile read error. + + Incorrect profiles were shown in /proc/ccs/profile + if either CONFIG_SAKURA or CONFIG_TOMOYO is disabled. + +Fix 2009/03/02 + + @ Undelete CONFIG_TOMOYO_AUDIT option. + + While HDD-less systems can use profiles with MAX_GRANT_LOG=0 and + MAX_REJECT_LOG=0 , I undeleted CONFIG_TOMOYO_AUDIT option for saving + memory used for /proc/ccs/grant_log and /proc/ccs/reject_log interfaces. + +Fix 2009/03/13 + + @ Show only profile entry names ever specified. + + Even if an administrator specifies only COMMENT= and MAC_FOR_FILE= + entries for /proc/ccs/profile , all available profile entries are shown. + This was designed to help administrators to know what entries are + available, but sometimes makes administrators feel noisy because of + entries showing default values. + + Thus, I modified to show only profile entry names ever specified. + +Fix 2009/03/18 + + @ Add MAC_FOR_IOCTL functionality. + + To be able to restrict ioctl() requests, I added MAC_FOR_IOCTL + functionality. + + This functionality requires modification of ccs-patch-\*.diff . + + @ Use better name for socket's pathname. + + Until now, socket's pathname was represented as "socket:[\$]" format + where \$ is inode's number. But inode's number is useless for name based + access control. Therefore, I modified to represent socket's pathname as + "socket:[family=\$:type=\$:protocol=\$]" format. + + This will help administrator to control ioctl() against sockets more + precisely. + + @ Fix misplaced ccs_capable() call. (only 2.6.8-\* and 2.6.9-\*) + + Location to insert ccs_capable(TOMOYO_SYS_IOCTL) in sys_ioctl() was + wrong since version 1.1 . + + @ Insert ccs_check_ioctl_permission() call. + + To make MAC_FOR_IOCTL functionality working, I inserted + ccs_check_ioctl_permission() call into ccs-patch-\*.diff . + +Fix 2009/03/23 + + @ Move sysctl()'s check from ccs-patch-\*.diff to fs/tomoyo_file.c . + + Since try_parse_table() in kernel/sysctl.c is almost identical between + all versions, I moved that function to fs/tomoyo_file.c . + + @ Relocate definitions and functions. + + To reduce exposed symbols, I relocated some definitions and functions. + +Fix 2009/03/24 + + @ Add CONFIG_TOMOYO_BUILTIN_INITIALIZERS option. + + Some systems don't have /sbin/modprobe and /sbin/hotplug . + Thus, I made these pathnames configurable. + +Version 1.6.7 2009/04/01 Feature enhancement release. + +Fix 2009/04/06 + + @ Drop "undelete domain" command. + + I added "undelete domain" command on 2007/01/19, but never used by policy + management tools. The garbage collector I added on 2007/01/29 will + automatically reuse memory and allow administrators switch domain policy + periodically, provided that the administrator kills processes in old + domains before recreating new domains with the same domainnames. + + Thus, I dropped "undelete domain" command. + + @ Escape invalid characters in ccs_check_mount_permission2(). + + ccs_check_mount_permission2() was passing unencoded strings to printk() + and ccs_update_mount_acl() and ccs_check_supervisor(). This may cause + /proc/ccs/system_policy and /proc/ccs/query to contain invalid + characters within a string. + +Fix 2009/04/07 + + @ Fix IPv4's "address_group" handling error. + + Since 1.6.5 , due to lack of ntohl() (byte order conversion) in + ccs_update_address_group_entry(), "address_group" with IPv4 address was + not working. + + This problem happens on little endian platforms (e.g. x86). + +Fix 2009/05/08 + + @ Add condition for symlink's target pathname. + + Until now, "allow_symlink" keyword allows creation of a symlink but does + not check the symlink's target. Usually it is no problem because + permission checks are done using dereferenced pathname. But in some + cases, we should restrict the symlink's target. For example, + "ln -s .htpasswd /var/www/html/readme.html" by CGI program should be + blocked because we will allow Apache to read both + /var/www/html/readme.html and /var/www/html/.htpasswd . + + Thus, I added new condition, "symlink.target". + + allow_symlink /var/www/html/\*.html if symlink.target="\*.html" + + allow_symlink /var/www/html/\*\-.\* if symlink.target="\*\-.\*" + + @ Don't return -EAGAIN at ccs_socket_recvmsg_permission(). + + It turned out that it is not permitted for accept() and recvmsg() to + return -EAGAIN if poll() said connections/datagrams are ready. However, + recvmsg() may return -EAGAIN and potentially confuse some applications + because ccs_socket_recvmsg_permission() is returning -EAGAIN. + + Thus, I modified ccs_socket_recvmsg_permission() to return -ENOMEM + rather than -EAGAIN. + +Fix 2009/05/19 + + @ Don't call get_fs_type() with a mutex held. + + Until now, when ccs_update_mount_acl() is called with unsupported + filesystem, /sbin/modprobe is executed from get_fs_type() to load + filesystem module. And get_fs_type() does not return until /sbin/modprobe + finishes. + + This means that it will cause deadlock if /sbin/modprobe (which is + executed via get_fs_type() in ccs_update_mount_acl()) calls + ccs_update_mount_acl(); although it won't happen unless an administrator + inserts execute_handler to call mount() requests in learning mode or to + add "allow_mount" entries to /proc/ccs/system_policy . + + I modified to unlock the mutex before calling get_fs_type(). + +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 2008/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 the strings + used in "if" clause) 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, + major device number, minor device number. "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 keyword "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() suceeds. + + 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.