1496 |
which causes /proc/ccs/grant_log contain whitespace characters |
which causes /proc/ccs/grant_log contain whitespace characters |
1497 |
if execute handler's pathname contains whitespace characters. |
if execute handler's pathname contains whitespace characters. |
1498 |
|
|
1499 |
|
Fix 2008/06/25 |
1500 |
|
|
1501 |
|
@ Return 0 when ccs_may_umount() succeeds. |
1502 |
|
|
1503 |
|
I forgot to clear error value in ccs_may_umount() when the requested |
1504 |
|
directory didn't match "deny_unmount" keyword. As a result, any umount() |
1505 |
|
request with RESTRICT_UNMOUNT=enforcing returned -EPERM error. |
1506 |
|
|
1507 |
Version 1.6.2 2008/06/25 Usability enhancement release. |
Version 1.6.2 2008/06/25 Usability enhancement release. |
1508 |
|
|
1509 |
|
Fix 2008/07/01 |
1510 |
|
|
1511 |
|
@ Fix "Compilation failure" with 2.4.20 kernel. |
1512 |
|
|
1513 |
|
RedHat Linux 9's 2.4.20 kernel backported O(1) scheduler patch, |
1514 |
|
resulting compilation error at ccs_load_policy(). |
1515 |
|
I added defined(TASK_DEAD) check. |
1516 |
|
|
1517 |
|
Fix 2008/07/08 |
1518 |
|
|
1519 |
|
@ Don't check permissions if vfsmount is NULL. |
1520 |
|
|
1521 |
|
Some filesystems (e.g. unionfs) pass NULL vfsmount. |
1522 |
|
I changed fs/tomoyo_file.c not to try to calculate pathnames |
1523 |
|
if vfsmount is NULL. |
1524 |
|
|
1525 |
|
Version 1.6.3 2008/07/15 Bug fix release. |
1526 |
|
|
1527 |
|
Fix 2008/08/21 |
1528 |
|
|
1529 |
|
@ Add workaround for gcc 4.3's bug. |
1530 |
|
|
1531 |
|
In some environments, fs/tomoyo_network.c could not be compiled |
1532 |
|
because of gcc 4.3's bug. |
1533 |
|
I modified save_ipv6_address() to use "integer literal" value |
1534 |
|
instead for "static const u8" variable. |
1535 |
|
|
1536 |
|
@ Change prototypes of some functions. |
1537 |
|
|
1538 |
|
To support 2.6.27 kernels, I replaced "struct nameidata" with |
1539 |
|
"struct path" for some functions. |
1540 |
|
|
1541 |
|
@ Detect distributor specific patches automatically. |
1542 |
|
|
1543 |
|
Since kernels with AppArmor patch applied is increasing, |
1544 |
|
I introduced a mechanism which determines whether specific patches |
1545 |
|
are applied or not, based on "#define" directives in the patches. |
1546 |
|
|
1547 |
|
Fix 2008/08/29 |
1548 |
|
|
1549 |
|
@ Remove "-ccs" suffix from Makefile's EXTRAVERSION. |
1550 |
|
|
1551 |
|
To reduce conflicts on Makefile's EXTRAVERSION, |
1552 |
|
I removed "-ccs" suffix from ccs-patch-2.\*.diff . |
1553 |
|
Those who build kernels without using specs/build-\*.sh , |
1554 |
|
please edit EXTRAVERSION tag manually so that original kernels |
1555 |
|
will not be overwritten by TOMOYO Linux kernels. |
1556 |
|
|
1557 |
|
Version 1.6.4 2008/09/03 Minor update release. |
1558 |
|
|
1559 |
|
Fix 2008/09/09 |
1560 |
|
|
1561 |
|
@ Add "try again" response to "delayed enforcing" mode. |
1562 |
|
|
1563 |
|
To be able to handle pathname changes caused by software updates, |
1564 |
|
"delayed enforcing" mode was introduced. It allows administrator to |
1565 |
|
grant access requests which are about to be rejected by the kernel. |
1566 |
|
|
1567 |
|
To be able to handle pathname changes caused by software updates better, |
1568 |
|
I introduced "try again" response. As "delayed enforcing" mode sleeps |
1569 |
|
a process which violated policy, administrator can update policy while |
1570 |
|
the process is sleeping. This "try again" response allows administrator |
1571 |
|
to restart policy checks from the beginning after updating policy. |
1572 |
|
|
1573 |
|
Fix 2008/09/11 |
1574 |
|
|
1575 |
|
@ Remember whether the process is allowed to write to /proc/ccs/ interface. |
1576 |
|
|
1577 |
|
Since programs for manipulating policy (e.g. ccs-queryd ) are installed |
1578 |
|
in the form of RPM/DEB packages, these programs lose the original |
1579 |
|
pathnames when they are updated by the package manager. The package |
1580 |
|
manager renames these programs before deleting these programs so that |
1581 |
|
the package manager can rollback the operation. |
1582 |
|
This causes a problem when the programs are listed into /proc/ccs/manager |
1583 |
|
using pathnames, as the programs will no longer be allowed to write to |
1584 |
|
/proc/ccs/ interface while the process of old version of the program is |
1585 |
|
alive. |
1586 |
|
|
1587 |
|
To solve this problem, I modified to remember the fact that the process |
1588 |
|
is once allowed to write to /proc/ccs/ interface until the process |
1589 |
|
attempts to execute a different program. |
1590 |
|
This change makes it impossible to revoke permission to write to |
1591 |
|
/proc/ccs/ interface without killing the process, but it will be better |
1592 |
|
than nonfunctioning ccs-queryd program. |