Bhargava Shastry wrote: > 1. I have compiled 2.6.32 kernel for android with Tomoyo enabled and > activated but the problem is that for some reason Tomoyo Security Filesystem > is not getting mounted at /sys/kernel/security/tomoyo . This being the > default path for look-up of policy configuration files, certain tomoyo tools > e.g. tomoyo-editpolicy fail. I was wondering how I could mount tomoyo > security fs successfully at /sys/kernel/security.
There is no "Tomoyo Security Filesystem". /sys/kernel/security/tomoyo is within "Security Filesystem" which can be mounted by mount -t securityfs none /sys/kernel/security/ after mount -t sysfs none /sys/ . Since /sys/ will be automatically mounted upon boot and TOMOYO's tools internally mount /sys/kernel/security/ if not yet mounted, there should be nothing to worry. > 2. I have cross-compiled the ncurses library (used by Tomoyo tools) for the > Android platform but am unable to evoke Tomoyo tools' Graphical user > interface. Is it possible to get a GUI working on adb shell for example? Excuse me, tomoyo-editpolicy uses CUI. I don't know how to use GUI from "adb shell". Also, I don't know whether the terminal on the Android platform controlled by the ncurses library is functional enough to use tomoyo-editpolicy. You should consider using tomoyo-editpolicy-agent rather than tomoyo-editpolicy because you can communicate with the phone using adb. http://android-dls.com/wiki/index.php?title=ADB I guess there is nothing difficult with using tomoyo-editpolicy-agent on the phone because tomoyo-editpolicy-agent is a tiny application that communicates with tomoyo-editpolicy etc. running on the PC using TCP socket connection. "adb forward" will take care of forwarding TCP socket connection. http://androidforums.com/application-development/12060-adb-forward-error.html _______________________________________________ tomoyo-users-en mailing list [email protected] http://lists.sourceforge.jp/mailman/listinfo/tomoyo-users-en
