I have always wondered about why this warning is shown: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Googling a bit, it seems that maybe we are not setting the caps capabilities properly: http://unix.stackexchange.com/questions/20451/gnome-keyring-daemon-couldnt-allocate-secure-memory It looks like Arch is setting it to cap_ipc_lock=ep while we don't set the "ep" part :/ https://projects.archlinux.org/svntogit/packages.git/tree/trunk/gnome-keyring.install?h=packages/gnome-keyring
Bleh, per this it looks like it's ok: # getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon = cap_ipc_lock+ep I don't know then why this message is shown :S
You probably need to increase memlock limit. :) $ ulimit -l 64 $ pwsafe -l WARNING: pwsafe unable to use secure ram (need to be setuid root) Enter passphrase for /home/xxx/.pwsafe.dat: $ echo '@users - memlock 256' | sudo tee /etc/security/limits.d/memlock.conf @users - memlock 256 (relogin) $ ulimit -l 256 $ pwsafe -l Enter passphrase for /home/xxx/.pwsafe.dat:
No, I was wrong. Setting capabilities to cap_ipc_lock=ep should eliminate the need of increasing limits. =/
This still shows up.
[ccing security and myself because possible relevance.]
This was fixed at some point
