Summary: | gnome-base/gnome-keyring-3.16.0-r1: couldn't allocate secure memory to keep passwords and or keys from being written to the disk | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | alexander, jstein, marc_wippermann, sam, security |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
2015-10-21 11:26:38 UTC
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.] |