Date: Sun, 22 Apr 2012 22:06:41 -0500 From: Jeremy Messenger <mezz.freebsd@gmail.com> To: AN <andy@neu.net> Cc: gnome@freebsd.org Subject: Re: Unable to allocate secure memory from gnome-keyring Message-ID: <CADLFttd0JwjLZyoaVzjWZPE8dNSBptphOooxy6r9VYKuykBXTg@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1204222157150.55889@mail.neu.net> References: <alpine.BSF.2.00.1204222157150.55889@mail.neu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 22, 2012 at 9:12 PM, AN <andy@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 =A0 =A0 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL =A0am= d64 > > seahorse-2.32.0_6 =A0 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 secret= s > > Apr 22 18:46:06 FBSD10 gnome-keyring-daemon[954]: couldn't allocate secur= e > 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 g= rab > keyboard: 3 > Apr 22 18:46:11 FBSD10 gnome-keyring-prompt: couldn't allocate secure mem= ory > 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 byt= es > 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 t= o > the disk > > =A0seahorse-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 --=20 mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLFttd0JwjLZyoaVzjWZPE8dNSBptphOooxy6r9VYKuykBXTg>