| 1 |
On Sat, 2003-11-01 at 06:54, gOA-pSY wrote: |
| 2 |
> There is already a security framework initialized, register_security failed. |
| 3 |
> Failure registering capabilities with the kernel |
| 4 |
> selinux_register_security: Registering secondary module capability |
| 5 |
> Capability LSM initialized |
| 6 |
|
| 7 |
This means that the Capability LSM module couldn't register as the |
| 8 |
primary module (since SELinux is the primary). Then the next message |
| 9 |
means that it registers as a secondary module with SELinux. This is |
| 10 |
normal. |
| 11 |
|
| 12 |
> is it normal that doing this creates the following kernel messages? |
| 13 |
|
| 14 |
All of these denials are because you are running in the staff_r role. |
| 15 |
You need to be in the sysadm_r role to do a relabel and initrd. |
| 16 |
|
| 17 |
-- |
| 18 |
Chris PeBenito |
| 19 |
<pebenito@g.o> |
| 20 |
Developer, SELinux |
| 21 |
Hardened Gentoo Linux |
| 22 |
|
| 23 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
| 24 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |
Archives