Mon 28 May 2007 03:08:22 PM UTC, original submission:
Hi
I try to configure / make dazuko 2.3.3 with different configurations but using lsm (standard config) getting some errors within lsm api definiotion I think ...
--------------------
notebook1:/home/mazi1802/dazuko-2.3.3 # ./configure
checking host system type... Linux
checking for make utility... ok (make)
checking for C compiler... ok (cc)
kernel source in /lib/modules/2.6.21-170-default/source... yes
kernel build source in /lib/modules/2.6.21-170-default/build... yes
acquiring Linux kernel code configuration... ok
checking if Linux is RSBAC patched... no
checking if devfs is enabled... no
discovered host system... Linux (2.6.21)
checking if security module support is enabled... yes
verifying capabilities are not built-in... ok
locating LSM API header... ok
identifying LSM API (this can take a while)... ok
identifying device API... ok
inspecting class type... ok (class)
inspecting suspend function... ok (suspend2)
checking whether __d_path() is exported... yes
inspecting task_struct structure... ok (using parent)
disabling ON_CLOSE events (not available for Linux 2.6 LSM)
configure: creating Makefile
configure: creating library/Makefile
configure: creating example_c/Makefile
./configure successful
...
--------------------
using syscall hooking having some other problems ..
--------------------
notebook1:/home/mazi1802/dazuko-2.3.3 # ./configure --enable-syscalls --mapfile=/boot/System.map-2.6.21-170-default
checking host system type... Linux
checking for make utility... ok (make)
checking for C compiler... ok (cc)
kernel source in /lib/modules/2.6.21-170-default/source... yes
kernel build source in /lib/modules/2.6.21-170-default/build... yes
acquiring Linux kernel code configuration... ok
checking if Linux is RSBAC patched... no
checking if devfs is enabled... no
discovered host system... Linux (2.6.21)
checking for System.map file... ok (/boot/System.map-2.6.21-170-default)
locating sys_call_table... ok (0xffffffff803f32a0)
checking sys_call_table status... read-only
IMPORTANT NOTE:
If you get a kernel panic or segmentation fault while loading
the Dazuko module, you will need to reboot and try to
configure Dazuko again with the --sct-readonly option.
locating do_execve... ok (0xffffffff8023b10b)
identifying device API... ok
inspecting class type... ok (class)
inspecting suspend function... ok (suspend2)
checking whether __d_path() is exported... yes
inspecting task_struct structure... ok (using parent)
disabling ON_EXEC events (only available on x86 platforms)
configure: creating Makefile
configure: creating library/Makefile
configure: creating example_c/Makefile
./configure successful
=======================
Configuration summary
=======================
module events = ON_OPEN ON_CLOSE
devfs support = no
rsbac support = no
hooking via syscalls = yes
local __d_path() = no
module debug = no
library 1.x compatibility = yes
...
--------------------
Any ideas? Sorry for long post with error logs ... more in attached file
THX
Martin
|