| 1146 |
|
|
| 1147 |
Fix 2008/02/05 |
Fix 2008/02/05 |
| 1148 |
|
|
| 1149 |
@ Use find_task_by_vpid() instead of find_task_pid(). |
@ Use find_task_by_vpid() instead of find_task_by_pid(). |
| 1150 |
|
|
| 1151 |
Kernel 2.6.24 introduced PID namespace. |
Kernel 2.6.24 introduced PID namespace. |
| 1152 |
To search PID given from userland, the kernel needs to use |
To search PID given from userland, the kernel needs to use |
| 1153 |
find_task_by_vpid() instead of find_task_pid(). |
find_task_by_vpid() instead of find_task_by_pid(). |
| 1154 |
|
|
| 1155 |
Fix 2008/02/14 |
Fix 2008/02/14 |
| 1156 |
|
|
| 1428 |
echo Private: 1048576 > /proc/ccs/meminfo |
echo Private: 1048576 > /proc/ccs/meminfo |
| 1429 |
|
|
| 1430 |
Version 1.6.1 2008/05/10 Bug fix release. |
Version 1.6.1 2008/05/10 Bug fix release. |
| 1431 |
|
|
| 1432 |
|
Fix 2008/06/04 |
| 1433 |
|
|
| 1434 |
|
@ Check open mode of /proc/ccs/ interface. |
| 1435 |
|
|
| 1436 |
|
It turned out that I can avoid allocating memory for reading if |
| 1437 |
|
FMODE_READ is not set and memory for writing if FMODE_WRITE is not set. |
| 1438 |
|
|
| 1439 |
|
@ Wait for completion of /sbin/ccs-init . |
| 1440 |
|
|
| 1441 |
|
Since 2.4 kernel's call_usermodehelper() can't wait for termination of |
| 1442 |
|
the executed program, I was using the close() request of |
| 1443 |
|
/proc/ccs/meminfo to indicate that loading policy has finished. |
| 1444 |
|
But since /proc/ccs/meminfo could be accessed for setting memory quota |
| 1445 |
|
by /etc/ccs/ccs-post-init , I stopped using the close() request. |
| 1446 |
|
The policy loader no longer need to access /proc/ccs/meminfo to notify |
| 1447 |
|
the kernel that loading policy has finished. |
| 1448 |
|
|
| 1449 |
|
Fix 2008/06/05 |
| 1450 |
|
|
| 1451 |
|
@ Fix realpath for pipes and sockets. |
| 1452 |
|
|
| 1453 |
|
Kernel 2.6.22 and later use different method for calculating d_path(). |
| 1454 |
|
Since fs/realpath.c didn't notice the change, the realpath of pipes |
| 1455 |
|
appeared as "pipe:" rather than "pipe:[\$]" when they are opened via |
| 1456 |
|
/proc/PID/fd/ directory. |
| 1457 |
|
|
| 1458 |
|
@ Add process's information into /proc/ccs/query . |
| 1459 |
|
|
| 1460 |
|
While /proc/ccs/grant_log and /proc/ccs/reject_log contain process's |
| 1461 |
|
information, /proc/ccs/query doesn't contain it. |
| 1462 |
|
To be able to utilize ccs-queryd and ccs-notifyd more, I added it into |
| 1463 |
|
/proc/ccs/query . |
| 1464 |
|
|
| 1465 |
|
Fix 2008/06/10 |
| 1466 |
|
|
| 1467 |
|
@ Allow using patterns for globally readable files. |
| 1468 |
|
|
| 1469 |
|
To allow users specify locale specific files to globally readable files, |
| 1470 |
|
I relaxed checking in update_globally_readable_entry(). |
| 1471 |
|
|
| 1472 |
|
Fix 2008/06/11 |
| 1473 |
|
|
| 1474 |
|
@ Remove ALLOW_ENFORCE_GRACE parameter. |
| 1475 |
|
|
| 1476 |
|
Since unexpected requests caused by doing software updates can happen |
| 1477 |
|
in all profiles, users likely have to write ALLOW_ENFORCE_GRACE=enabled |
| 1478 |
|
to all profiles. And it makes meaningless to allow users to selectively |
| 1479 |
|
enable specific profile's ALLOW_ENFORCE_GRACE parameter. |
| 1480 |
|
So, I removed ALLOW_ENFORCE_GRACE parameter. |
| 1481 |
|
Now, the system behaves as if ALLOW_ENFORCE_GRACE=enabled is specified. |
| 1482 |
|
The behavior of "delayed enforcing" mode is defined in the following |
| 1483 |
|
order. |
| 1484 |
|
|
| 1485 |
|
(1) The requests are rejected immediately if nobody is opening |
| 1486 |
|
/proc/ccs/query interface. |
| 1487 |
|
(2) The requests will be rejected in 10 seconds if somebody other than |
| 1488 |
|
ccs-queryd (such as less(1)) is opening /proc/ccs/query interface, |
| 1489 |
|
for such process doesn't write dummy decisions. |
| 1490 |
|
|
| 1491 |
|
Fix 2008/06/22 |
| 1492 |
|
|
| 1493 |
|
@ Pass escaped pathname to audit_execute_handler_log(). |
| 1494 |
|
|
| 1495 |
|
I was passing unescaped pathname to audit_execute_handler_log() |
| 1496 |
|
which causes /proc/ccs/grant_log contain whitespace characters |
| 1497 |
|
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. |
| 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. |
TOMOYO
Parent Directory
Revision Log
Patch