Make sure everything linked to the module was compiled with
-fno-stack-protector. Try using CC="gcc -fno-stack-protector".
CC didn't help. But maybe it's just that the module is being compiled
against usbatm kernel module and that's how SSP got into the build? Have
a look at part of the makefile:
KERNELDIR := /lib/modules/$(shell uname -r)/build
obj-m := ueagle-atm.o
ueagle-atm-objs := ueagle.o
all:
$(MAKE) -C $(KERNELDIR) M=$(PWD) EXTRA_CFLAGS=-DDEBUG
Here is what I get in detail:
[code]
pkg ueagle:/usr/src/ueagle/ueagle-atm-svn> CC="gcc -fno-stack-protector"
make
make -C /lib/modules/2.6.11.12-grsec/build
M=/usr/src/ueagle/ueagle-atm-svn EXTRA_CFLAGS=-DDEBUG
make[1]: Entering directory `/usr/src/kernel/linux-2.6.11.12'
Building modules, stage 2.
MODPOST
*** Warning: "__guard" [/usr/src/ueagle/ueagle-atm-svn/ueagle-atm.ko]
undefined!
*** Warning: "__stack_smash_handler"
[/usr/src/ueagle/ueagle-atm-svn/ueagle-atm.ko] undefined!
make[1]: Leaving directory `/usr/src/kernel/linux-2.6.11.12'
[/code]
...and however I try to get rid of SSP through env flags, it stays just
the same.
--
David Ciecierski
Want control, education, and security from your operating system?
Hardened Linux From Scratch
http://www.linuxfromscratch.org/hlfs
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
