Unable to allocate secure memory from gnome-keyring

[Jeremy Messenger]

On Sun, Apr 22, 2012 at 9:12 PM, AN <andy at neu.net> wrote:
> After a recent portupgrade (Sun Apr 22 22:03:42 EDT 2012), I see the
> following in /var/log/messages and from the command line.
>
> FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #11 r234399: Tue Apr 17
> 18:15:12 EDT 2012     root at FBSD10:/usr/obj/usr/src/sys/MYKERNEL  amd64
>
> seahorse-2.32.0_6   GNOME application for managing encryption keys (PGP,
> SSH)
> seahorse-plugins-2.30.1_6 Plug-ins for the Seahorse key and password
> management appli
> gnome-keyring-2.32.1_1 A program that keeps passwords and other secrets
> libgnome-keyring-2.32.0_1 A program that keeps passwords and other secrets
>
> Apr 22 18:46:06 FBSD10 gnome-keyring-daemon[954]: couldn't allocate secure
> memory to keep passwords and or keys from being written to the disk
> Apr 22 18:46:07 FBSD10 gnome-keyring-prompt: could not grab keyboard: 3
> Apr 22 18:46:07 FBSD10 gnome-keyring-daemon[954]: ** Message: could not grab
> keyboard: 3
> Apr 22 18:46:11 FBSD10 gnome-keyring-prompt: couldn't allocate secure memory
> to keep passwords and or keys from being written to the disk
> Apr 22 18:46:11 FBSD10 gnome-keyring-daemon[954]: couldn't lock 16384 bytes
> of private memory: Resource temporarily unavailable
> Apr 22 18:46:11 FBSD10 gnome-keyring-daemon[954]: ** Message: couldn't
> allocate secure memory to keep passwords and or keys from being written to
> the disk
>
>  seahorse-daemon
> couldn't lock 16384 bytes of private memory: Resource temporarily
> unavailable

Don't think I have seen this before, but I never use seahorse though.
You should update your -CURRENT as Jason has committed numbers of fix
in the jemalloc.

> ** (process:42587): WARNING **: Unable to allocate secure memory from
> gnome-keyring.
>
>
> ** (process:42587): WARNING **: Proceeding using insecure memory for
> password fields.

Both of warnings here are known for age. I don't remember exactly why,
I think it's something that FreeBSD lacks of what Linux has or maybe
just need to complete port to FreeBSD. I am not sure.

Cheers,
Mezz


-- 
mezz.freebsd at gmail.com - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org