| 797 |
I was using PAGE_SIZE (4096 in many environments) |
I was using PAGE_SIZE (4096 in many environments) |
| 798 |
as the max length of any string data. |
as the max length of any string data. |
| 799 |
But for environments that have larger PAGE_SIZE, |
But for environments that have larger PAGE_SIZE, |
| 800 |
doing memset(ptr, 0, PAGE_SIZE) everytime is too wasteful. |
doing memset(ptr, 0, PAGE_SIZE) every time is too wasteful. |
| 801 |
|
|
| 802 |
Fix 2007/01/29 |
Fix 2007/01/29 |
| 803 |
|
|
| 1723 |
to see process information. The content of /proc/ccs/.execute_handler is |
to see process information. The content of /proc/ccs/.execute_handler is |
| 1724 |
identical to /proc/ccs/.process_status . |
identical to /proc/ccs/.process_status . |
| 1725 |
|
|
| 1726 |
Version 1.6.5 2008/11/11 Third anniversary release. |
Version 1.6.5 2008/11/11 Third anniversary release. |
| 1727 |
|
|
| 1728 |
Fix 2008/12/01 |
Fix 2008/12/01 |
| 1729 |
|
|
| 2243 |
/proc/ccs/profile (which results in not protecting the system at all), |
/proc/ccs/profile (which results in not protecting the system at all), |
| 2244 |
I added a check for PROFILE_VERSION= . |
I added a check for PROFILE_VERSION= . |
| 2245 |
|
|
| 2246 |
Version 1.7.1 2009/11/11 Fourth anniversary release. |
Version 1.7.1 2009/11/11 Fourth anniversary release. |
| 2247 |
|
|
| 2248 |
Fix 2009/11/13 |
Fix 2009/11/13 |
| 2249 |
|
|
| 2382 |
Since 1.7.0 , ccs_lport_reserved() was by error checking wrong port |
Since 1.7.0 , ccs_lport_reserved() was by error checking wrong port |
| 2383 |
number. As a result, "deny_autobind" keyword was not working as expected. |
number. As a result, "deny_autobind" keyword was not working as expected. |
| 2384 |
|
|
| 2385 |
Version 1.7.2 2010/04/01 Feature enhancement release. |
Version 1.7.2 2010/04/01 Feature enhancement release. |
| 2386 |
|
|
| 2387 |
Fix 2010/04/10 |
Fix 2010/04/10 |
| 2388 |
|
|
| 2441 |
permissions (e.g. allow_env PATH if symlink.target="/"), it triggered |
permissions (e.g. allow_env PATH if symlink.target="/"), it triggered |
| 2442 |
NULL pointer dereference. |
NULL pointer dereference. |
| 2443 |
|
|
| 2444 |
Fix 2010/10/05 |
Fix 2010/10/28 |
| 2445 |
|
|
| 2446 |
|
@ Fix umount() pathname calculation. |
| 2447 |
|
|
| 2448 |
|
"mount --bind /path/to/file1 /path/to/file2" is legal. |
| 2449 |
|
Therefore, "umount /path/to/file2" is also legal. |
| 2450 |
|
Do not automatically append trailing '/' if pathname to be unmounted |
| 2451 |
|
does not end with '/'. |
| 2452 |
|
|
| 2453 |
|
@ Add preserve KABI compatibility option. (2.6 kernels only) |
| 2454 |
|
|
| 2455 |
|
TOMOYO needs "struct ccs_domain_info *" and "u32" for each |
| 2456 |
|
"struct task_struct". But embedding these variables into |
| 2457 |
|
"struct task_struct" breaks KABI for prebuilt kernel modules (which |
| 2458 |
|
means that you will need to rebuild prebuilt kernel modules). |
| 2459 |
|
|
| 2460 |
|
Since KABI is commonly used (compared to 5 years ago), asking users to |
| 2461 |
|
rebuild kernel modules which are not included in kernel package is no |
| 2462 |
|
longer preferable. Therefore, I added a new option that keeps |
| 2463 |
|
"struct task_struct" unmodified in order to keep KABI. |
| 2464 |
|
|
| 2465 |
|
Note that you have to use ccs-patch-2.6.\*.diff which patches |
| 2466 |
|
kernel/fork.c in order to use this option. Otherwise, TOMOYO will leak |
| 2467 |
|
memory whenever "struct task_struct" is released. |
| 2468 |
|
|
| 2469 |
@ Change directives. |
@ Change directives. |
| 2470 |
|
|
| 2503 |
when you have to disable access control for recv() operation due to |
when you have to disable access control for recv() operation due to |
| 2504 |
application breakage by discarding incoming datagram. |
application breakage by discarding incoming datagram. |
| 2505 |
|
|
|
@ Wait for next connection/datagram if current connection/datagram was |
|
|
discarded. |
|
|
|
|
|
Regarding "network inet stream accept", "network inet dgram recv", |
|
|
"network inet raw recv" directives, I modified to wait for next |
|
|
connection/datagram if current connection/datagram was discarded. |
|
|
LSM hooks for these directives are currently missing because this |
|
|
behavior may break applications. If you found applications broken by |
|
|
this behavior, you can set CONFIG::network::inet_stream_accept and/or |
|
|
CONFIG::network::inet_dgram_recv and/or CONFIG::network::inet_raw_recv |
|
|
to mode=disabled in order to only disable filtering for incoming |
|
|
connection/datagram. |
|
|
|
|
| 2506 |
@ Add Unix domain socket restriction support. |
@ Add Unix domain socket restriction support. |
| 2507 |
|
|
| 2508 |
Until now, it was possible to restrict only inet domain sockets (i.e. |
Until now, it was possible to restrict only inet domain sockets (i.e. |
| 2659 |
|
|
| 2660 |
This change allows you to jump to arbitrary domain. |
This change allows you to jump to arbitrary domain. |
| 2661 |
|
|
| 2662 |
|
Note that this change also reverts "Change /proc/ccs/info/self_domain ." |
| 2663 |
|
made on 2006/10/24. Now, 'cat < /proc/ccs/info/self_domain' will act like |
| 2664 |
|
'cat /proc/ccs/info/self_domain'. Programs depending on old assumption |
| 2665 |
|
need to be updated. |
| 2666 |
|
|
| 2667 |
@ Add "task auto_domain_transition". |
@ Add "task auto_domain_transition". |
| 2668 |
|
|
| 2669 |
This is similar to "task manual_domain_transition", but is automatically |
This is similar to "task manual_domain_transition", but is automatically |
| 2677 |
task manual_domain_transition <kernel> //./non-root task.uid!=0 |
task manual_domain_transition <kernel> //./non-root task.uid!=0 |
| 2678 |
|
|
| 2679 |
will jump to "<kernel> //./non-root" domain if current process's UID is |
will jump to "<kernel> //./non-root" domain if current process's UID is |
| 2680 |
not 0 and current process wrote "<kernel> //./non-root" + '\n' to |
not 0 and current process wrote "<kernel> //./non-root" to |
| 2681 |
/proc/ccs/.transition interface. |
/proc/ccs/self_domain interface. |
| 2682 |
|
|
| 2683 |
If domain transition failed, current process will be killed by SIGKILL |
If domain transition failed, current process will be killed by SIGKILL |
| 2684 |
signal. |
signal. |
| 2687 |
|
|
| 2688 |
I merged similar code in order to reduce object's filesize. |
I merged similar code in order to reduce object's filesize. |
| 2689 |
|
|
| 2690 |
Version 1.8.0 2010/XX/XX Feature enhancement release. |
Version 1.8.0 2010/11/11 Fifth anniversary release. |
| 2691 |
|
|
| 2692 |
|
Fix 2010/12/01 |
| 2693 |
|
|
| 2694 |
|
@ Use same interface for audit logs. |
| 2695 |
|
|
| 2696 |
|
To be able to perform fine grained filtering by /usr/sbin/ccs-auditd , |
| 2697 |
|
I merged /proc/ccs/grant_log and /proc/ccs/reject_log as |
| 2698 |
|
/proc/ccs/audit and added granted=yes or granted=no to audit logs. |
| 2699 |
|
|
| 2700 |
|
Fix 2010/12/17 |
| 2701 |
|
|
| 2702 |
|
@ Split ccs_null_security into ccs_default_security and ccs_oom_security. |
| 2703 |
|
|
| 2704 |
|
ccs_null_security is used by preserve KABI compatibility option and is |
| 2705 |
|
used for providing default values against threads which have not yet |
| 2706 |
|
allocated memory for their security contexts. |
| 2707 |
|
|
| 2708 |
|
If current thread failed to allocate memory for current thread's security |
| 2709 |
|
context, current thread uses ccs_null_security. Since current thread is |
| 2710 |
|
allowed to modify current thread's security context, current thread might |
| 2711 |
|
modify ccs_null_security which should not be modified for any reason. |
| 2712 |
|
|
| 2713 |
|
Therefore, I split ccs_null_security into ccs_default_security and |
| 2714 |
|
ccs_oom_security and use ccs_oom_security when current thread failed to |
| 2715 |
|
allocate memory for current thread's security context. |
| 2716 |
|
|
| 2717 |
|
Threads which do not share ccs_oom_security are not affected by threads |
| 2718 |
|
which share ccs_oom_security. Threads which share ccs_oom_security will |
| 2719 |
|
experience temporary inconsistency, but such threads are about to be |
| 2720 |
|
killed by SIGKILL signal. |
| 2721 |
|
|
| 2722 |
|
Fix 2011/01/11 |
| 2723 |
|
|
| 2724 |
|
@ Use filesystem name for unnamed devices when vfsmount is missing. |
| 2725 |
|
|
| 2726 |
|
"Change pathname for non-rename()able filesystems." changed to use |
| 2727 |
|
"$fsname:" if the filesystem does not support rename() operation and |
| 2728 |
|
"dev($major,$minor):" otherwise when vfsmount is missing. But it turned |
| 2729 |
|
out that it is useless to use "dev($major,$minor):" for unnamed devices |
| 2730 |
|
(filesystems with $major == 0). Thus, I changed to use "$fsname:" rather |
| 2731 |
|
than "dev($major,$minor):" for filesystems with $major == 0 when vfsmount |
| 2732 |
|
is missing. |
| 2733 |
|
|
| 2734 |
|
Fix 2011/02/07 |
| 2735 |
|
|
| 2736 |
|
@ Fix infinite loop bug when reading /proc/ccs/audit or /proc/ccs/query . |
| 2737 |
|
|
| 2738 |
|
In ccs_flush(), head->r.w[0] holds pointer to string data to be printed. |
| 2739 |
|
But head->r.w[0] was updated only when the string data was partially |
| 2740 |
|
printed (because head->r.w[0] will be updated by head->r.w[1] later if |
| 2741 |
|
completely printed). However, regarding /proc/ccs/audit and |
| 2742 |
|
/proc/ccs/query , an additional '\0' is printed after the string data was |
| 2743 |
|
completely printed. But if free space for read buffer became 0 before |
| 2744 |
|
printing the additional '\0', ccs_flush() was returning without updating |
| 2745 |
|
head->r.w[0]. As a result, ccs_flush() forever reprints already printed |
| 2746 |
|
string data. |
| 2747 |
|
|
| 2748 |
|
Fix 2011/03/01 |
| 2749 |
|
|
| 2750 |
|
@ Run garbage collector without waiting for /proc/ccs/ users. |
| 2751 |
|
|
| 2752 |
|
Currently TOMOYO holds SRCU lock upon open() and releases it upon close() |
| 2753 |
|
because list elements stored in the "struct ccs_io_buffer" instances are |
| 2754 |
|
accessed until close() is called. However, such SRCU usage causes lockdep |
| 2755 |
|
to complain about leaving the kernel with SRCU lock held. Therefore, |
| 2756 |
|
I changed to hold/release SRCU upon each read()/write() by selectively |
| 2757 |
|
deferring kfree() by keeping track of the "struct ccs_io_buffer" |
| 2758 |
|
instances. |
| 2759 |
|
|
| 2760 |
|
Fix 2011/03/05 |
| 2761 |
|
|
| 2762 |
|
@ Support built-in policy configuration. |
| 2763 |
|
|
| 2764 |
|
To be able to start using enforcing mode from the early stage of boot |
| 2765 |
|
sequence, I added support for built-in policy configuration and |
| 2766 |
|
activating access control without calling external policy loader program. |
| 2767 |
|
|
| 2768 |
|
This will be useful for systems where operations which can lead to the |
| 2769 |
|
hijacking of the boot sequence are needed before loading the policy. |
| 2770 |
|
For example, you can activate immediately after loading the fixed part of |
| 2771 |
|
policy which will allow only operations needed for mounting a partition |
| 2772 |
|
which contains the variant part of policy and verifying (e.g. running GPG |
| 2773 |
|
check) and loading the variant part of policy. Since you can start using |
| 2774 |
|
enforcing mode from the beginning, you can reduce the possibility of |
| 2775 |
|
hijacking the boot sequence. |
| 2776 |
|
|
| 2777 |
|
Fix 2011/03/10 |
| 2778 |
|
|
| 2779 |
|
@ Remove /proc/ccs/meminfo interface. |
| 2780 |
|
|
| 2781 |
|
Please use /proc/ccs/stat interface instead. |
| 2782 |
|
|
| 2783 |
|
Fix 2011/03/15 |
| 2784 |
|
|
| 2785 |
|
@ Pack policy when printing via /proc/ccs/ interface. |
| 2786 |
|
|
| 2787 |
|
The kernel side is ready for accepting packed input like |
| 2788 |
|
|
| 2789 |
|
file read/write/execute /path/to/file |
| 2790 |
|
|
| 2791 |
|
but was using unpacked output like |
| 2792 |
|
|
| 2793 |
|
file read /path/to/file |
| 2794 |
|
file write /path/to/file |
| 2795 |
|
file execute /path/to/file |
| 2796 |
|
|
| 2797 |
|
because most of userland tools were not ready for accepting packed input. |
| 2798 |
|
|
| 2799 |
|
The advantages of using packed policy are that it makes policy files |
| 2800 |
|
smaller and it speeds up loading/saving policy files. |
| 2801 |
|
|
| 2802 |
|
Since most of userland tools are ready for accepting packed input by now, |
| 2803 |
|
I changed to use packed policy for both input and output. |
| 2804 |
|
|
| 2805 |
|
Fix 2011/03/31 |
| 2806 |
|
|
| 2807 |
|
@ Fix conditional policy parsing. |
| 2808 |
|
|
| 2809 |
|
Since exec.realpath= and symlink.target= accept path_group, |
| 2810 |
|
symlink.target="@foo" was by error parsed as symlink.target=@foo . |
| 2811 |
|
|
| 2812 |
|
@ Serialize updating profile's comment line. |
| 2813 |
|
|
| 2814 |
|
We need to serialize when updating COMMENT= line in /proc/ccs/profile . |
| 2815 |
|
|
| 2816 |
|
Version 1.8.1 2011/04/01 Usability enhancement with "Zettai, Daijoubudayo" release! |
| 2817 |
|
|
| 2818 |
|
Fix 2011/04/03 |
| 2819 |
|
|
| 2820 |
|
@ Fix fcntl(F_SETFL, O_APPEND) handling. |
| 2821 |
|
|
| 2822 |
|
Since 1.8.0, TOMOYO was by error checking "file write" permission rather |
| 2823 |
|
than "file append" permission when changing file's writing mode from |
| 2824 |
|
"overwriting" to "append". |
| 2825 |
|
|
| 2826 |
|
This error should impact little (except CentOS 6.0 kernels) because once |
| 2827 |
|
a file was opened for "overwriting" mode, changing that file to "append" |
| 2828 |
|
mode cannot undo overwriting the file. Regarding CentOS 6.0 kernels, |
| 2829 |
|
due to different ACC_MODE definition, TOMOYO was by error needlessly |
| 2830 |
|
checking "file read" permission when fcntl() was requested. |
| 2831 |
|
|
| 2832 |
|
Fix 2011/04/20 |
| 2833 |
|
|
| 2834 |
|
@ Remove unused "struct inode *" parameter from hooks. |
| 2835 |
|
|
| 2836 |
|
Since pre-vfs functions were removed on 2010/09/18, "struct inode *" |
| 2837 |
|
parameter which was used for checking parent directory's DAC permission |
| 2838 |
|
is no longer used. |
| 2839 |
|
|
| 2840 |
|
Note that "struct ccsecurity_operations ccsecurity_ops" has changed. |
| 2841 |
|
Loadable kernel modules that depends on it need to be rebuilt. |
| 2842 |
|
|
| 2843 |
|
Fix 2011/05/05 |
| 2844 |
|
|
| 2845 |
|
@ Fix wrong profile number in audit logs for "misc env" permission. |
| 2846 |
|
|
| 2847 |
|
Profile number used for "file execute" permission was by error reused |
| 2848 |
|
when generating audit logs for "misc env" permission. |
| 2849 |
|
|
| 2850 |
|
Fix 2011/05/11 |
| 2851 |
|
|
| 2852 |
|
@ Fix wrong domainname validation. |
| 2853 |
|
|
| 2854 |
|
"<kernel>" + "/foo/\" + "/bar" was by error checked when |
| 2855 |
|
"<kernel> /foo/\* /bar" was given. As a result, legal domainnames like |
| 2856 |
|
"<kernel> /foo/\* /bar" are rejected. |
| 2857 |
|
|
| 2858 |
|
Fix 2011/06/06 |
| 2859 |
|
|
| 2860 |
|
@ Add policy namespace support. |
| 2861 |
|
|
| 2862 |
|
To be able to use TOMOYO in LXC environments, I introduced policy |
| 2863 |
|
namespace. Each policy namespace has its own set of domain policy, |
| 2864 |
|
exception policy and profiles, which are all independent of other |
| 2865 |
|
namespaces. |
| 2866 |
|
|
| 2867 |
|
@ Remove CONFIG_CCSECURITY_BUILTIN_INITIALIZERS option. |
| 2868 |
|
|
| 2869 |
|
From now on, exception policy and manager need to be able to handle |
| 2870 |
|
policy namespace (which is a <$namespace> prefix added to each line). |
| 2871 |
|
Thus, space-separated list for CONFIG_CCSECURITY_BUILTIN_INITIALIZERS is |
| 2872 |
|
no longer suitable for handling policy namespace. |
| 2873 |
|
|
| 2874 |
|
Fix 2011/06/10 |
| 2875 |
|
|
| 2876 |
|
@ Allow specifying trigger for activation. |
| 2877 |
|
|
| 2878 |
|
To be able to use TOMOYO under systemd environments where init= parameter |
| 2879 |
|
is used, I changed to allow overriding the trigger for calling external |
| 2880 |
|
policy loader and activating MAC via kernel command line options. |
| 2881 |
|
|
| 2882 |
|
Fix 2011/06/14 |
| 2883 |
|
|
| 2884 |
|
@ Remove unused "struct inode *" parameter from ccs-patch-\*.diff . |
| 2885 |
|
|
| 2886 |
|
To follow changes I made on 2011/04/20, I removed "struct inode *" from |
| 2887 |
|
ccs_mknod_permission(), ccs_mkdir_permission(), ccs_rmdir_permission(), |
| 2888 |
|
ccs_unlink_permission(), ccs_symlink_permission(), ccs_link_permission(), |
| 2889 |
|
ccs_rename_permission() that are called from fs/namei.c |
| 2890 |
|
net/unix/af_unix.c include/linux/security.c security/security.c . |
| 2891 |
|
If you have your own ccs-patch-*.diff , please update accordingly. |
| 2892 |
|
|
| 2893 |
|
Version 1.8.2 2011/06/20 Usability enhancement release. |
| 2894 |
|
|
| 2895 |
|
Fix 2011/07/07 |
| 2896 |
|
|
| 2897 |
|
@ Remove /proc/ccs/.domain_status interface. |
| 2898 |
|
|
| 2899 |
|
Writing to /proc/ccs/.domain_status can be emulated by |
| 2900 |
|
|
| 2901 |
|
( echo "select " $domainname; echo "use_profile " $profile ) | |
| 2902 |
|
/usr/sbin/ccs-loadpolicy -d |
| 2903 |
|
|
| 2904 |
|
and reading from /proc/ccs/.domain_status can be emulated by |
| 2905 |
|
|
| 2906 |
|
grep -A 1 '^<' /proc/ccs/domain_policy | |
| 2907 |
|
awk ' { if ( domainname == "" ) { if ( substr($1, 1, 1) == "<" ) |
| 2908 |
|
domainname = $0; } else if ( $1 == "use_profile" ) { |
| 2909 |
|
print $2 " " domainname; domainname = ""; } } ; ' |
| 2910 |
|
|
| 2911 |
|
. Since this interface is used by only /usr/sbin/ccs-setprofile , |
| 2912 |
|
remove this interface by updating /usr/sbin/ccs-setprofile . |
| 2913 |
|
|
| 2914 |
|
Fix 2011/07/09 |
| 2915 |
|
|
| 2916 |
|
@ Fix /proc/ccs/stat parser. |
| 2917 |
|
|
| 2918 |
|
For optimization, I changed to use simple_strtoul() rather than sscanf() |
| 2919 |
|
in ccs_write_stat(). But it caused parsing failure if space is inserted |
| 2920 |
|
before value (e.g. "Memory used by policy: $value"). |
| 2921 |
|
|
| 2922 |
|
Fix 2011/07/13 |
| 2923 |
|
|
| 2924 |
|
@ Accept "::" notation for IPv6 address. |
| 2925 |
|
|
| 2926 |
|
In order to add network access restriction to TOMOYO 2.4, I backported |
| 2927 |
|
routines for parsing/printing IPv4/IPv6 address from kernel 3.0 into |
| 2928 |
|
TOMOYO 1.8.2. |
| 2929 |
|
Now, IPv6 address accepts "::1" instead of "0:0:0:0:0:0:0:1". |
TOMOYO
Parent Directory
Revision Log
Patch