[rsbac] UM can't set passwords - strange symptoms

Andrew Dobbie adobbie at ieee.org
Mon Jul 16 23:30:23 CEST 2007

Maybe if you are in softmode you will be able to run that command as
root and set the password. I'm guessing user secoff does not have 
CAP_IPC_LOCK and therefor cannot lock memory.

On Mon, 2007-16-07 at 21:16 +0200, Sven Seeland wrote:
> Hi everybody,
> I'm having some problems with the RSBAC usermanagement module. I've recently 
> reinstalled my server and am now switching to the RSBAC UM system. However, I 
> can't set any passwords and therefore I can't log in.
> When issuing
> 	$ rsbac_usermod -p some_password secoff
> I always get the following as a response:
> 	Unable to lock password into physical memory!
> No errors in the logs though. /proc/rsbac/rmsg doesn't say anything, and I don't 
> get any other log messages either.
> Any ideas what might be causing this?
> I'm using RSBAC 1.3.4(-r1) in a 2.6.21 Kernel (Gentoo RSBAC patchset out of 
> Portage) glibc 2.5(-r4 out of portage as well). Apparently libnss_rsbac.la 
> doesn't link correctly against librsbac.la - or so says revdep-rebuild. 
> Recompiling rsbac-admin doesn't fix this.
> Any ideas? Help is greatly appreciated.
> Thank you,
> Sven
> _______________________________________________
> rsbac mailing list
> rsbac at rsbac.org
> http://www.rsbac.org/mailman/listinfo/rsbac

More information about the rsbac mailing list