オープンソース・ソフトウェアの開発とダウンロード

Subversion リポジトリの参照

Diff of /trunk/1.8.x/ccs-patch/README.ccs

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2003 by kumaneko, Wed Dec 24 07:07:28 2008 UTC revision 2459 by kumaneko, Mon Apr 20 05:47:21 2009 UTC
# Line 1753  Fix 2008/12/01 Line 1753  Fix 2008/12/01
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
# Line 1796  Fix 2008/12/24 Line 1796  Fix 2008/12/24
1796    
1797        I meant to print SYAORAN-ERROR: message when error == -EPERM,        I meant to print SYAORAN-ERROR: message when error == -EPERM,
1798        but I was printing it when error == 0 since 1.6.0 .        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    Fix 2009/01/28
1808    
1809        @ Fix "allow_read" + "allow_write" != "allow_read/write" problem.
1810    
1811          Since 1.6.0 , due to a bug in ccs_update_single_path_acl(),
1812          appending "allow_read/write" entry didn't update internal "allow_read"
1813          and "allow_write" entries. As a result, attempt to open(O_RDWR) succeeds
1814          but open(O_RDONLY) and open(O_WRONLY) fail.
1815    
1816          Workaround is to write an entry twice when newly appending that entry.
1817          If written twice, internal "allow_read" and "allow_write" entries
1818          are updated.
1819    
1820    Fix 2009/02/26
1821    
1822        @ Fix profile read error.
1823    
1824          Incorrect profiles were shown in /proc/ccs/profile
1825          if either CONFIG_SAKURA or CONFIG_TOMOYO is disabled.
1826    
1827    Fix 2009/03/02
1828    
1829        @ Undelete CONFIG_TOMOYO_AUDIT option.
1830    
1831          While HDD-less systems can use profiles with MAX_GRANT_LOG=0 and
1832          MAX_REJECT_LOG=0 , I undeleted CONFIG_TOMOYO_AUDIT option for saving
1833          memory used for /proc/ccs/grant_log and /proc/ccs/reject_log interfaces.
1834    
1835    Fix 2009/03/13
1836    
1837        @ Show only profile entry names ever specified.
1838    
1839          Even if an administrator specifies only COMMENT= and MAC_FOR_FILE=
1840          entries for /proc/ccs/profile , all available profile entries are shown.
1841          This was designed to help administrators to know what entries are
1842          available, but sometimes makes administrators feel noisy because of
1843          entries showing default values.
1844    
1845          Thus, I modified to show only profile entry names ever specified.
1846    
1847    Fix 2009/03/18
1848    
1849        @ Add MAC_FOR_IOCTL functionality.
1850    
1851          To be able to restrict ioctl() requests, I added MAC_FOR_IOCTL
1852          functionality.
1853    
1854          This functionality requires modification of ccs-patch-\*.diff .
1855    
1856        @ Use better name for socket's pathname.
1857    
1858          Until now, socket's pathname was represented as "socket:[\$]" format
1859          where \$ is inode's number. But inode's number is useless for name based
1860          access control. Therefore, I modified to represent socket's pathname as
1861          "socket:[family=\$:type=\$:protocol=\$]" format.
1862    
1863          This will help administrator to control ioctl() against sockets more
1864          precisely.
1865    
1866        @ Fix misplaced ccs_capable() call.  (only 2.6.8-\* and 2.6.9-\*)
1867    
1868          Location to insert ccs_capable(TOMOYO_SYS_IOCTL) in sys_ioctl() was
1869          wrong since version 1.1 .
1870    
1871        @ Insert ccs_check_ioctl_permission() call.
1872    
1873          To make MAC_FOR_IOCTL functionality working, I inserted
1874          ccs_check_ioctl_permission() call into ccs-patch-\*.diff .
1875    
1876    Fix 2009/03/23
1877    
1878        @ Move sysctl()'s check from ccs-patch-\*.diff to fs/tomoyo_file.c .
1879    
1880          Since try_parse_table() in kernel/sysctl.c is almost identical between
1881          all versions, I moved that function to fs/tomoyo_file.c .
1882    
1883        @ Relocate definitions and functions.
1884    
1885          To reduce exposed symbols, I relocated some definitions and functions.
1886    
1887    Fix 2009/03/24
1888    
1889        @ Add CONFIG_TOMOYO_BUILTIN_INITIALIZERS option.
1890    
1891          Some systems don't have /sbin/modprobe and /sbin/hotplug .
1892          Thus, I made these pathnames configurable.
1893    
1894    Version 1.6.7 2009/04/01   Feature enhancement release.
1895    
1896    Fix 2009/04/06
1897    
1898        @ Drop "undelete domain" command.
1899    
1900          I added "undelete domain" command on 2007/01/19, but never used by policy
1901          management tools. The garbage collector I added on 2007/01/29 will
1902          automatically reuse memory and allow administrators switch domain policy
1903          periodically, provided that the administrator kills processes in old
1904          domains before recreating new domains with the same domainnames.
1905    
1906          Thus, I dropped "undelete domain" command.
1907    
1908        @ Escape invalid characters in ccs_check_mount_permission2().
1909    
1910          ccs_check_mount_permission2() was passing unencoded strings to printk()
1911          and ccs_update_mount_acl() and ccs_check_supervisor(). This may cause
1912          /proc/ccs/system_policy and /proc/ccs/query to contain invalid
1913          characters within a string.
1914    
1915    Fix 2009/04/07
1916    
1917        @ Fix IPv4's "address_group" handling error.
1918    
1919          Since 1.6.5 , due to lack of ntohl() (byte order conversion) in
1920          ccs_update_address_group_entry(), "address_group" with IPv4 address was
1921          not working.
1922    
1923          This problem happens on little endian platforms (e.g. x86).
1924    
1925    Fix 2009/04/20
1926    
1927        @ Update recvmsg() hooks.
1928    
1929          Since 1.5.0, I was doing network access control for incoming UDP and RAW
1930          packets inside skb_recv_datagram(). But to synchronize with LSM version,
1931          I moved ccs_recv_datagram_permission() hook from skb_recv_datagram() to
1932          udp_recvmsg()/udpv6_recvmsg()/raw_recvmsg()/rawv6_recvmsg() with name
1933          change to ccs_recvmsg_permission().

Legend:
Removed from v.2003  
changed lines
  Added in v.2459

Back to OSDN">Back to OSDN
ViewVC Help
Powered by ViewVC 1.1.26