| 1753 |
new conditions for checking file's type and permissions. |
new conditions for checking file's type and permissions. |
| 1754 |
For example, |
For example, |
| 1755 |
|
|
| 1756 |
allow_read /etc/fstab if path1.type=regular path1.perm=0644 |
allow_read /etc/fstab if path1.type=file path1.perm=0644 |
| 1757 |
|
|
| 1758 |
will allow opening /etc/fstab for reading only if /etc/fstab is a regular |
will allow opening /etc/fstab for reading only if /etc/fstab is a regular |
| 1759 |
file and it's permission is 0644, and |
file and it's permission is 0644, and |
| 1791 |
|
|
| 1792 |
To be able to tell whether a symbol is TOMOYO Linux related or not, |
To be able to tell whether a symbol is TOMOYO Linux related or not, |
| 1793 |
I added "ccs_" prefix as much as possible. |
I added "ccs_" prefix as much as possible. |
| 1794 |
|
|
| 1795 |
|
@ Fix ccs_check_flags() error message. |
| 1796 |
|
|
| 1797 |
|
I meant to print SYAORAN-ERROR: message when error == -EPERM, |
| 1798 |
|
but I was printing it when error == 0 since 1.6.0 . |
| 1799 |
|
|
| 1800 |
|
Fix 2009/01/05 |
| 1801 |
|
|
| 1802 |
|
@ Use kmap_atomic()/kunmap_atomic() for reading "struct linux_binprm". |
| 1803 |
|
|
| 1804 |
|
As remove_arg_zero() uses kmap_atomic(KM_USER0), I modified to use |
| 1805 |
|
kmap_atomic(KM_USER0) rather than kmap(). |
| 1806 |
|
|
| 1807 |
|
@ Relocate definitions and functions. |
| 1808 |
|
|
| 1809 |
|
To reduce exposed symbols, I relocated some definitions and functions. |
| 1810 |
|
|
| 1811 |
|
Fix 2009/01/28 |
| 1812 |
|
|
| 1813 |
|
@ Fix "allow_read" + "allow_write" != "allow_read/write" problem. |
| 1814 |
|
|
| 1815 |
|
Since 1.6.0 , due to a bug in ccs_update_single_path_acl(), |
| 1816 |
|
appending "allow_read/write" entry didn't update internal "allow_read" |
| 1817 |
|
and "allow_write" entries. As a result, attempt to open(O_RDWR) succeeds |
| 1818 |
|
but open(O_RDONLY) and open(O_WRONLY) fail. |
| 1819 |
|
|
| 1820 |
|
Workaround is to write an entry twice when newly appending that entry. |
| 1821 |
|
If written twice, internal "allow_read" and "allow_write" entries |
| 1822 |
|
are updated. |
| 1823 |
|
|
| 1824 |
|
Fix 2009/02/26 |
| 1825 |
|
|
| 1826 |
|
@ Fix profile read error. |
| 1827 |
|
|
| 1828 |
|
Incorrect profiles were shown in /proc/ccs/profile |
| 1829 |
|
if either CONFIG_SAKURA or CONFIG_TOMOYO is disabled. |
| 1830 |
|
|
| 1831 |
|
Fix 2009/03/02 |
| 1832 |
|
|
| 1833 |
|
@ Undelete CONFIG_TOMOYO_AUDIT option. |
| 1834 |
|
|
| 1835 |
|
While HDD-less systems can use profiles with MAX_GRANT_LOG=0 and |
| 1836 |
|
MAX_REJECT_LOG=0 , I undeleted CONFIG_TOMOYO_AUDIT option for saving |
| 1837 |
|
memory used for /proc/ccs/grant_log and /proc/ccs/reject_log interfaces. |
| 1838 |
|
|
| 1839 |
|
Fix 2009/03/13 |
| 1840 |
|
|
| 1841 |
|
@ Show only profile entry names ever specified. |
| 1842 |
|
|
| 1843 |
|
Even if an administrator specifies only COMMENT= and MAC_FOR_FILE= |
| 1844 |
|
entries for /proc/ccs/profile , all available profile entries are shown. |
| 1845 |
|
This was designed to help administrators to know what entries are |
| 1846 |
|
available, but sometimes makes administrators feel noisy because of |
| 1847 |
|
entries showing default values. |
| 1848 |
|
|
| 1849 |
|
Thus, I modified to show only profile entry names ever specified. |
| 1850 |
|
|
| 1851 |
|
Version 1.6.7 2009/??/?? Feature enhancement release. |
TOMOYO
Parent Directory
Revision Log
Patch