<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:dc="http://purl.org/dc/elements/1.1/">
 <channel>
  <pubDate>Sat, 23 Feb 2013 07:35:37 GMT</pubDate>
  <description>公開されたフォーラムでどなたでも参照、投稿できます</description>
  <link>http://en.sourceforge.jp/projects/tomoyo/forums/</link>
  <atom:link href="http://en.sourceforge.jp/forum/rss.php?group_id=1973&amp;forum_id=11352" rel="self" type="application/rss+xml" />
  <title>Forum: Open Discussion - TOMOYO on SourceForge.JP</title>
  <language>ja-jp</language>
  <item>
   <pubDate>Sat, 23 Feb 2013 07:35:37 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: &quot;Reverse&quot; sandbox possible?</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=67463</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=67463</guid>
   <description>Hello.

&gt; I'm wondering if it's possible to create some kind of reverse sandbox with
&gt; tomoyo linux 2.0.
&gt; What I want is to deny everything access to one specific folder, except one
&gt; program.
&gt; Specificlly I only want the bitcoin client and nothing else to be able to
&gt; acces ~/.bitcoin/

So far, only \- operator is possible. That is, define a path_group like

  path_group ALL_BUT_BITCOIN /\*\-home/\*
  path_group ALL_BUT_BITCOIN /\*\-home/\{\*\}/
  path_group ALL_BUT_BITCOIN /\*\-home/\{\*\}/\*
  path_group ALL_BUT_BITCOIN /home/\*\-.bitcoin/
  path_group ALL_BUT_BITCOIN /home/\*\-.bitcoin/\*
  path_group ALL_BUT_BITCOIN /home/\*\-.bitcoin/\{\*\}/
  path_group ALL_BUT_BITCOIN /home/\*\-.bitcoin/\{\*\}/\*

and define an acl_group like

  acl_group 0 file read @ALL_BUT_BITCOIN
  acl_group 0 file write @ALL_BUT_BITCOIN

and let each domain refer that acl_group using use_group keyword.

  use_group 0



If you can use CaitSith ( http://I-love.SAKURA.ne.jp/tomoyo/CaitSith-en.pdf )
instead of TOMOYO 2.x, then CaitSith would be easier to achieve that.
Rules in CaitSith will look like below.

  0 acl read path=&quot;/home/\*/.bitcoin/\(\*\)/\*&quot;
    audit 0
    0 allow task.exe=&quot;/path/to/bitcoin/client&quot;
    1 deny

  0 acl write path=&quot;/home/\*/.bitcoin/\(\*\)/\*&quot;
    audit 0
    0 allow task.exe=&quot;/path/to/bitcoin/client&quot;
    1 deny

I demonstrated only read and write operations. But you need to be also careful
about pathname manipulation operations like rename/link/mount.

If you can move ~/.bitcoin/ directory to a dedicated partition and have a
symlink to the dedicated partition, you can use attributes of the dedicated
partition (e.g. path.major and path.minor) for conditions to restrict access.

  0 acl read path.major=XX path.minor=XX
    audit 0
    0 allow task.exe=&quot;/path/to/bitcoin/client&quot;
    1 deny

  0 acl write path.major=XX path.minor=XX
    audit 0
    0 allow task.exe=&quot;/path/to/bitcoin/client&quot;
    1 deny
</description>
  </item>
  <item>
   <pubDate>Fri, 22 Feb 2013 23:10:42 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>&quot;Reverse&quot; sandbox possible?</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=67462</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=67462</guid>
   <description>Hi,

I'm wondering if it's possible to create some kind of reverse sandbox with tomoyo linux 2.0.
What I want is to deny everything access to one specific folder, except one program.
Specificlly I only want the bitcoin client and nothing else to be able to acces ~/.bitcon/


Thanks,
Anonymous user</description>
  </item>
  <item>
   <pubDate>Fri, 07 Sep 2012 01:10:15 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: How ccsecurity works as loadable kernelmodule</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=65429</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=65429</guid>
   <description>I forwarded your question at http://www.spinics.net/linux/fedora/linux-security-module/msg14300.html but got little response.
Please see http://vger.kernel.org/vger-lists.html#linux-security-module and
post your opinion to linux-security-module ML.
</description>
  </item>
  <item>
   <pubDate>Sat, 11 Aug 2012 07:54:27 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>How ccsecurity works as loadable kernelmodule</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=65054</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=65054</guid>
   <description>how tomoyo 1.7/1.8x work as loadable kernel module?
Is it possible to minimize boot time by making tomoyo 2.5 as loadable kernel module ?</description>
  </item>
  <item>
   <pubDate>Mon, 08 Dec 2008 10:10:15 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>RE: tomoyo and 2.6.26</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=40498</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=40498</guid>
   <description>oh, thank you :&gt;
i'm ashamed that i didn't find earlier :~
once again- thank you very much :&gt;
</description>
  </item>
  <item>
   <pubDate>Mon, 08 Dec 2008 05:50:31 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: tomoyo and 2.6.26</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=40491</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=40491</guid>
   <description>Please see http://lists.sourceforge.jp/mailman/archives/tomoyo-users-en/2008-December/000010.html

Thanks.
</description>
  </item>
  <item>
   <pubDate>Mon, 08 Dec 2008 02:41:11 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>tomoyo and 2.6.26</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=40489</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=40489</guid>
   <description>hi.
i've got some problems with kernel and tomoyo.
i've downloaded the newest version of tomoyo - ccs-patch-1.6.5-20081111 and kernel (well... not the newest) from kernel.org
could anyone tell me what I'm doing wrong?

root@samantha:/usr/src/linux-2.6.26# patch -p1 &lt;/usr/src/linux-2.6.26/ccs-patch-2.6.26.diff
patching file arch/ia64/ia32/sys_ia32.c
patching file arch/mips/kernel/ptrace32.c
patching file fs/Kconfig
patching file fs/Makefile
patching file fs/attr.c
patching file fs/compat.c
patching file fs/compat_ioctl.c
patching file fs/exec.c
patching file fs/fcntl.c
patching file fs/ioctl.c
patching file fs/namei.c
Hunk #2 succeeded at 1597 (offset -15 lines).
Hunk #3 succeeded at 1659 (offset -15 lines).
Hunk #4 succeeded at 1722 (offset -15 lines).
Hunk #5 succeeded at 2100 (offset -15 lines).
Hunk #6 succeeded at 2135 (offset -15 lines).
Hunk #7 succeeded at 2230 (offset -15 lines).
Hunk #8 succeeded at 2349 (offset -15 lines).
Hunk #9 succeeded at 2418 (offset -15 lines).
Hunk #10 succeeded at 2446 (offset -15 lines).
Hunk #11 succeeded at 2518 (offset -15 lines).
Hunk #12 succeeded at 2542 (offset -15 lines).
Hunk #13 succeeded at 2623 (offset -15 lines).
Hunk #14 succeeded at 2653 (offset -15 lines).
Hunk #15 succeeded at 2889 (offset -15 lines).
Hunk #16 succeeded at 2927 (offset -15 lines).
patching file fs/namespace.c
patching file fs/open.c
patching file fs/proc/Makefile
patching file fs/proc/proc_misc.c
patching file include/linux/init_task.h
patching file include/linux/sched.h
patching file kernel/compat.c
patching file kernel/kexec.c
patching file kernel/kmod.c
patching file kernel/module.c
patching file kernel/ptrace.c
patching file kernel/sched.c
Hunk #2 succeeded at 4641 (offset -59 lines).
patching file kernel/signal.c
Hunk #2 succeeded at 2202 (offset -1 lines).
Hunk #3 succeeded at 2269 (offset -1 lines).
Hunk #4 succeeded at 2288 (offset -1 lines).
patching file kernel/sys.c
patching file kernel/sysctl.c
patching file kernel/time.c
patching file kernel/time/ntp.c
patching file net/core/datagram.c
patching file net/ipv4/inet_connection_sock.c
patching file net/ipv4/inet_hashtables.c
patching file net/ipv4/udp.c
patching file net/socket.c
patching file net/unix/af_unix.c
root@samantha:/usr/src/linux-2.6.26# make clean
/usr/src/linux-2.6.26/fs/Makefile:123: /usr/src/linux-2.6.26/fs/Makefile-2.6.ccs: Nie ma takiego pliku ani katalogu
make[1]: *** Brak reguł do wykonania obiektu `/usr/src/linux-2.6.26/fs/Makefile-2.6.ccs'. Stop.
make: *** [_clean_fs] Błąd 2

////////////////
my translation:
:there is no such file or directory
:there is no rules to execute object 
:error 2
/////////////////


root@samantha:/usr/src/linux-2.6.26# make mrproper
/usr/src/linux-2.6.26/fs/Makefile:123: /usr/src/linux-2.6.26/fs/Makefile-2.6.ccs: Nie ma takiego pliku ani katalogu
make[1]: *** Brak reguł do wykonania obiektu `/usr/src/linux-2.6.26/fs/Makefile-2.6.ccs'. Stop.
make: *** [_clean_fs] Błąd 2
root@samantha:/usr/src/linux-2.6.26# make menuconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/kxgettext.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/mconf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
scripts/kconfig/lex.zconf.c:1628: warning: ‘input’ defined but not used
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf arch/x86/Kconfig
fs/Kconfig:2167: can't open file &quot;fs/Kconfig.ccs&quot;
make[1]: *** [menuconfig] Błąd 1
make: *** [menuconfig] Błąd 2
root@samantha:/usr/src/linux-2.6.26#

I'm trying to do it on debian testing/lenny

your sincerely
RR</description>
  </item>
  <item>
   <pubDate>Thu, 20 Nov 2008 13:42:01 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>RE: subpolicy switchable inside of programs</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=40077</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=40077</guid>
   <description>Thanks for explanation. I hope that something like chhat with userspace lib will appear in future versions of tomoyo.

Note that this feature is optional in apparmor thus doesn't require any apps to be ported if they don't want to use this feature.
</description>
  </item>
  <item>
   <pubDate>Sat, 15 Nov 2008 06:30:51 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: subpolicy switchable inside of programs</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=39899</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=39899</guid>
   <description>Hello.

&gt; apparmor has one very cool feature that allows to define subpolices
&gt; (called HATs) for particular program, let say /usr/bin/whatever.
&gt; The program with API can switch between these subpolices and return back to
&gt; &quot;main&quot; policy.
&gt; 
&gt; This allows for example apache to have &quot;main&quot; policy that has access to
&gt; almost nothing and per virtual host subpolicies &quot;virtual1&quot; that gives access
&gt; to /home/www/virtual1, &quot;virtual2&quot; that gives access to /home/www/virtual2.
&gt; Now apache when serving virtual1 switches to &quot;virtual1&quot; subpolicy,
&gt; when finishes it goes back to &quot;main&quot;, then when serving virtual2 it switches
&gt; to &quot;virtual2&quot; subpolicy.
&gt; 
Yes. That's a practical and useful feature. The key point of AppArmor's way is
random values called &quot;magic&quot; which are used for chhat() function.

&gt; This is very nice feature. SELinux for example cannot do anything like that.
&gt; 
Right. This is because SELinux thinks that dropped privileges should not be
revived by userland. Returning to &quot;main&quot; policy by userland's operation is
a kind of privilege escalation which an attacker can use.

&gt; How this looks in Tomoyo? Could such feature be implemented (if it's not
&gt; already)
Regarding TOMOYO, so far there is no API for userland application.
There are several reasons.

One is that TOMOYO doesn't require modification of userland programs.
It is not a good thing to proliferate implementation specific APIs.
Forcing application program developers to support SELinux's API and AppArmor's
API and TOMOYO's API and more will burden the application developers. The worst
result is, application developers stop supporting none of these APIs.

Another one is that TOMOYO doesn't have hooks for fork() and exit() operations.
This means that TOMOYO can't allocate and free memory for per process storage
for storing &quot;magic&quot; value of chhat() function.
LSM has been providing hooks (security_task_alloc() and security_task_free())
for such purpose, but these hooks will be removed shortly by merging
&quot;Copy on write credentials&quot; patchset. I'm not sure AppArmor and TOMOYO can
revive these hooks.


By the way, TOMOYO 1.6.x supports process's state values which are controlled
by task.state[0] task.state[1] task.state[2] variables.
This feature can provide chhat() like functionality, but lacks &quot;magic&quot; values.
For example,

  &lt;kernel&gt; /usr/sbin/sshd /bin/bash
  allow_execute /bin/cat if task.uid=0 ; set task.state[0]=0
  allow_execute /bin/cat if task.uid!=0 ; set task.state[0]=1

  &lt;kernel&gt; /usr/sbin/sshd /bin/bash /bin/cat
  allow_read /tmp/file1 if task.state[0]=0
  allow_read /tmp/file2 if task.state[0]!=0

will allow root to read /tmp/file1 and non-root to read /tmp/file2 .
If you have a chance to insert some secret calls (which corresponds with
chhat()) within a process, you can use thse variables within a process.
</description>
  </item>
  <item>
   <pubDate>Thu, 13 Nov 2008 12:40:40 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>subpolicy switchable inside of programs</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=39872</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=39872</guid>
   <description>apparmor has one very cool feature that allows to define subpolices (called HATs) for particular program, let say /usr/bin/whatever. The program with API can switch between these subpolices and return back to &quot;main&quot; policy.

This allows for example apache to have &quot;main&quot; policy that has access to almost nothing and per virtual host subpolicies &quot;virtual1&quot; that gives access to /home/www/virtual1, &quot;virtual2&quot; that gives access to /home/www/virtual2. Now apache when serving virtual1 switches to &quot;virtual1&quot; subpolicy, when finishes it goes back to &quot;main&quot;, then when serving virtual2 it switches to &quot;virtual2&quot; subpolicy.

This is very nice feature. SELinux for example cannot do anything like that.

How this looks in Tomoyo? Could such feature be implemented (if it's not already)

Thanks</description>
  </item>
  <item>
   <pubDate>Wed, 03 Sep 2008 08:51:14 GMT</pubDate>
   <dc:creator>Toshiharu Harada (haradats)</dc:creator>
   <title>TOMOYO Linux version 1.6.4 released</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=38662</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=38662</guid>
   <description>Version 1.6.4 adds support for the following kernel versions:

- vanilla 2.6.27-rc5 kernel
- openSUSE 11.0's 2.6.25 kernel
- Ubuntu 8.10's 2.6.27 kernel
- Mandriva 2009.0's 2.6.27 kenrel

Now we have project pages at freshmeat and SourceForge.net.

http://freshmeat.net/projects/tomoyo/
http://sourceforge.net/projects/tomoyo/

How to activate TOMOYO Linux on Mandriva

- http://tomoyo.sourceforge.jp/en/1.6.x/1st-step/mandriva2008.1/

Release announce (read only) ml, &quot;tomoyo-announce&quot; just created

- https://lists.sourceforge.net/lists/listinfo/tomoyo-announce

Enjoy!
</description>
  </item>
  <item>
   <pubDate>Tue, 29 Jul 2008 10:07:56 GMT</pubDate>
   <dc:creator>Toshiharu Harada (haradats)</dc:creator>
   <title>new ml created for foreign users!</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=37881</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=37881</guid>
   <description>Please subscribe and enjoy!

http://lists.sourceforge.jp/mailman/listinfo/tomoyo-users-en
</description>
  </item>
  <item>
   <pubDate>Thu, 19 Jun 2008 05:40:32 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: Tomoyo linux cross reference/cypress_m8</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=37254</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=37254</guid>
   <description>Please try these packages.

http://osdn.dl.sourceforge.jp/tomoyo/30299/linux-image-2.6.24-19-ccs1.6.1_2.6.24-19.33_i386.deb
http://osdn.dl.sourceforge.jp/tomoyo/30299/linux-ubuntu-modules-2.6.24-19-ccs1.6.1_2.6.24-19.27_i386.deb
http://osdn.dl.sourceforge.jp/tomoyo/30299/linux-restricted-modules-2.6.24-19-ccs1.6.1_2.6.24.13-19.42_i386.deb
http://osdn.dl.sourceforge.jp/tomoyo/30299/linux-headers-2.6.24-19-ccs1.6.1_2.6.24-19.33_i386.deb
http://osdn.dl.sourceforge.jp/tomoyo/30299/linux-headers-lum-2.6.24-19-ccs1.6.1_2.6.24-19.27_i386.deb
</description>
  </item>
  <item>
   <pubDate>Thu, 19 Jun 2008 05:34:59 GMT</pubDate>
   <dc:creator>duong anh thi (anhthi)</dc:creator>
   <title>Tomoyo linux cross reference/cypress_m8</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=37253</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=37253</guid>
   <description>I have a problem with cypress_m8.c. When i build cypress_m8 project, terminal notice that &quot; cant't find *.h in /usr/linux/*.h&quot;. I want to install linux-headers-2.6.24-ccsq.6.1. How to install it in my Ubuntu i386. please help me.
Thanks a lot...</description>
  </item>
  <item>
   <pubDate>Mon, 16 Jun 2008 13:14:15 GMT</pubDate>
   <dc:creator>Toshiharu Harada (haradats)</dc:creator>
   <title>spamの消し方</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=37224</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=37224</guid>
   <description>数日前からこのフォーラムにspamと思われるメッセージが続けて投稿されています。ここは、誰でも書き込める場所としてあえて認証をかけておらず、できるだけ現状のままで運営したいと思っています。

tomoyo-devの方はスパムを含めてメッセージを削除できるよう設定していますので、この機会に削除方法を説明します。メッセージの削除は、SF.jpにログインした状態で、「フォーラム」のメニューから「管理(admin)」を選ぶと「削除」画面が表示されます。

削除は、該当するメッセージの&quot;msg_id&quot;を入力して行います（一度に削除できるのは1メッセージです）。msg_idは5桁の数値で、対象のメッセージを開いた状態で件名にフォーカスをあてると表示されます。存在しないmsg_idを入力するとエラーになります。

SF.jpの設定で「フォーラムをモニターする」を選択すると、該当するフォーラムで新しい発言があった場合にメールで通知されますが（私はこの設定を行っています）、そのメッセージではmsg_idが本文に記入されています。

本日(6/16)の夜7時以降スパムを削除しようとしたら、既になくなっており、どなたか削除いただいのだとわかりました。どうもありがとうございました。(_ _)</description>
  </item>
  <item>
   <pubDate>Tue, 23 Oct 2007 02:01:07 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: [BUG]: TOMOYO 1.5.1 ccs-init</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32925</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32925</guid>
   <description>I uploaded fixed version with same name.

Thnak you.
</description>
  </item>
  <item>
   <pubDate>Tue, 23 Oct 2007 00:01:47 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: [BUG]: TOMOYO 1.5.1 ccs-init</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32924</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32924</guid>
   <description>Oops! I lost '!' somewhere.

Thank you.
</description>
  </item>
  <item>
   <pubDate>Mon, 22 Oct 2007 13:59:58 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>[BUG]: TOMOYO 1.5.1 ccs-init</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32918</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32918</guid>
   <description>
select no default profile will kernel panic and stop booting.
maybe ! is lost in line 121:

    elif [ &quot;x$PROFILE&quot; != &quot;xdisable&quot; ]; then


</description>
  </item>
  <item>
   <pubDate>Mon, 22 Oct 2007 00:29:58 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: TOMOYO audit logs</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32887</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32887</guid>
   <description>Hello.

Thank you for your opinion.

Starting /usr/lib/ccs/ccs-auditd at /sbin/ccs-init would be possible
if /var/ partition is mounted read-write and /usr/ partition is mounted read-only,
but these partitions have to be mounted read-only at that moment
because fsck is called at /etc/rc.d/rc.sysinit .

TOMOYO can hold access logs up to MAX_GRANT_LOG and MAX_REJECT_LOG entries
in the kernel memory so that access logs won't be lost
when these partitions are not ready to write.
</description>
  </item>
  <item>
   <pubDate>Sat, 20 Oct 2007 13:43:07 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>TOMOYO audit logs</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32878</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32878</guid>
   <description>
# cat &gt; /etc/init.d/ccs-auditd &lt;&lt; EOF
#!/bin/sh
/usr/lib/ccs/ccs-auditd /dev/null /var/log/tomoyo/reject_log.txt
EOF
# chmod +x /etc/init.d/ccs-auditd

And create symbolic links to the script.

# update-rc.d ccs-auditd start 99 2 3 4 5 .
Adding system startup for /etc/init.d/ccs-auditd ...
/etc/rc2.d/S99ccs-auditd -&gt; ../init.d/ccs-auditd
/etc/rc3.d/S99ccs-auditd -&gt; ../init.d/ccs-auditd
/etc/rc4.d/S99ccs-auditd -&gt; ../init.d/ccs-auditd
/etc/rc5.d/S99ccs-auditd -&gt; ../init.d/ccs-auditd



it seems that  start audit log from /sbin/ccs-init might be better than from init.d .
1.  add a simple audit log config file  /etc/ccs/log.conf:
    timestamp=`date %F-%T`
    permit_log=/var/log/tomoyo/permit_log$timestamp.txt
    reject_log=/var/log/tomoyo/reject_log$timestamp.txt
2.  in ccs-init start autit log:
     . /etc/ccs/log.conf
     if touch $permit_log &amp;&amp; touch $reject_log; then /usr/lib/ccs/ccs-auditd $permit_log $reject_log  fi
3.  then start the selected policy
4.  if a log file is ordinary file(not /dev/null, /dev/console,etc), and not protected by any deny_rewrite item, automatically add to current Exception policy
deny_rewrite  /var/log/tomoyo/permit_log$timestamp.txt
deny_rewrite  /var/log/tomoyo/reject_log$timestamp.txt


so that audit logs are complete and protected, and file name could be timestamped for each boot when needed.


</description>
  </item>
  <item>
   <pubDate>Tue, 16 Oct 2007 16:37:11 GMT</pubDate>
   <dc:creator>Toshiharu Harada (haradats)</dc:creator>
   <title>added the link to</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32813</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32813</guid>
   <description>http://elinux.org/TomoyoLinux

thanks!</description>
  </item>
  <item>
   <pubDate>Tue, 16 Oct 2007 15:43:44 GMT</pubDate>
   <dc:creator>Toshiharu Harada (haradats)</dc:creator>
   <title>RE: http://cblfs.cross-lfs.org/index.php/TOMOYO</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32812</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32812</guid>
   <description>it's cool! :-)</description>
  </item>
  <item>
   <pubDate>Tue, 16 Oct 2007 15:24:47 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>http://cblfs.cross-lfs.org/index.php/TOMOYO</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32811</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32811</guid>
   <description>
http://cblfs.cross-lfs.org/index.php/TOMOYO</description>
  </item>
  <item>
   <pubDate>Mon, 15 Oct 2007 11:33:52 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: RE ask: make TOMOYO boot quickly</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32779</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32779</guid>
   <description>Updated.

http://svn.sourceforge.jp/cgi-bin/viewcvs.cgi?rev=580&amp;root=tomoyo&amp;view=rev</description>
  </item>
  <item>
   <pubDate>Mon, 15 Oct 2007 00:20:46 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: boot messag TOMOYO: 2.1.0-lkml-4   2007/1</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32763</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32763</guid>
   <description>&gt; 2. after it stops learning mode in this situation, which mode will be started?
It is a safeguard to avoid memory consumption.
Entries are no longer appended to that domain automatically.
That domain behaves as if a profile for permissive mode is assigned
although that domain is assigned a profile for learning mode.
</description>
  </item>
  <item>
   <pubDate>Mon, 15 Oct 2007 00:15:54 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: boot messag TOMOYO: 2.1.0-lkml-4   2007/1</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32762</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32762</guid>
   <description>Just ignore. They are harmless.

Pathnames for file_pattern directive must contain patterns.
But some of automatically generated entries don't contain patterns, and the kernel complains that 'This is not a valid file_pattern entry'.

Run 'savepolicy e' to exclude these invalid entries from /etc/tomoyo/exception_policy.conf .
</description>
  </item>
  <item>
   <pubDate>Mon, 15 Oct 2007 00:10:51 GMT</pubDate>
   <dc:creator>Tetsuo Handa (kumaneko)</dc:creator>
   <title>RE: what functions have been excluded?</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32761</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32761</guid>
   <description>Ability to restrict

(1) incoming TCP connection (allow_network TCP accept)
(2) incoming UDP datagrams  (allow_network UDP connect)
(3) incoming IP datagrams  (allow_network RAW connect)
(4) signal transmission    (allow_signal)

are excluded.
</description>
  </item>
  <item>
   <pubDate>Sat, 13 Oct 2007 05:30:53 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>RE: boot messag TOMOYO: 2.1.0-lkml-4   2007/1</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32750</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32750</guid>
   <description>1. there are many invalid pathname.
2. after it stops learning mode in this situation, which mode will be started?</description>
  </item>
  <item>
   <pubDate>Sat, 13 Oct 2007 05:25:20 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>boot messag TOMOYO: 2.1.0-lkml-4   2007/10/11</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32749</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32749</guid>
   <description>Freeing unused kernel memory: 160k freed
Clocksource tsc unstable (delta = 254787654 ns)
Time: pit clocksource has been installed.
tmy_add_pattern_entry: Invalid pathname '/proc/self/auxv'
tmy_add_pattern_entry: Invalid pathname '/proc/self/clear_refs'
tmy_add_pattern_entry: Invalid pathname '/proc/self/cmdline'
tmy_add_pattern_entry: Invalid pathname '/proc/self/coredump_filter'
tmy_add_pattern_entry: Invalid pathname '/proc/self/environ'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/0'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/1'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/2'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/3'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/4'
tmy_add_pattern_entry: Invalid pathname '/proc/self/fdinfo/5'
tmy_add_pattern_entry: Invalid pathname '/proc/self/maps'
tmy_add_pattern_entry: Invalid pathname '/proc/self/mem'
tmy_add_pattern_entry: Invalid pathname '/proc/self/mounts'
tmy_add_pattern_entry: Invalid pathname '/proc/self/mountstats'
tmy_add_pattern_entry: Invalid pathname '/proc/self/oom_adj'
tmy_add_pattern_entry: Invalid pathname '/proc/self/oom_score'
tmy_add_pattern_entry: Invalid pathname '/proc/self/sched'
tmy_add_pattern_entry: Invalid pathname '/proc/self/smaps'
tmy_add_pattern_entry: Invalid pathname '/proc/self/stat'
tmy_add_pattern_entry: Invalid pathname '/proc/self/statm'
tmy_add_pattern_entry: Invalid pathname '/proc/self/status'
tmy_add_pattern_entry: Invalid pathname '/proc/self/wchan'
TOMOYO: 2.1.0-lkml-4   2007/10/11
TOMOYO: Mandatory Access Control activated.
.
.
.
pccard: PCMCIA card inserted into slot 1
TOMOYO-WARNING: Domain '&lt;kernel&gt; /sbin/udevd' has so many ACLs to hold. Stopped learning mode.
cs: IO port probe 0x100-0x3af: excluding 0x130-0x137 0x200-0x207 0x220-0x22f 0x388-0x38f
.
.
.</description>
  </item>
  <item>
   <pubDate>Fri, 12 Oct 2007 14:11:00 GMT</pubDate>
   <dc:creator> (None)</dc:creator>
   <title>what functions have been excluded?</title>
   <link>http://en.sourceforge.jp/forum/message.php?msg_id=32737</link>
   <guid>http://en.sourceforge.jp/forum/message.php?msg_id=32737</guid>
   <description>
http://lkml.org/lkml/2007/10/11/140

This time, we excluded LSM expansion and related functions.

</description>
  </item>
 </channel>
</rss>
