grsecurity forums

Hello!

I've finally found some time to patch and configure a new kernel, at first it was a breeze, even managed to package it and get it onto an other box where I'd rather have no gcc & co. I've tried to package gradm too, and had some success (it seems to support $(DISTDIR) and dh_make and debuild kindly provided me with a package after all, but it could be broken as there aren't any udev rules in the package).

Then gradm gives me the error about the failed open syscall pointing to /dev/grsec. (/dev/grsec is there with major,minor being 1,13.) My question is, could this be because I have disabled RBAC during configuration, or it's because my half-assed packaging attempt? (Any way to list the registerd major,minor numbers? Or at least grep it easily from the .patch?)

Thanks in advance!

My tarball of gradm should have support in the makefile for creating the proper udev rules. I'm not exactly clear why you're running gradm on a system with RBAC disabled. Is it to test the 'make install' part of installing gradm? This runs gradm -P at the end of the installation, which will fail with an error if you do it on a system with RBAC disabled.

-Brad

I'm not exactly clear why you're running gradm on a system with RBAC disabled.

Basically, that's my question. Is it normal for gradm to fail as I've described if RBAC is disabled or not?

Yes, it's normal.

-Brad