From owner-freebsd-gnome@FreeBSD.ORG  Mon Apr 23 20:59:38 2012
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
Delivered-To: gnome@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id B9513106564A
	for <gnome@freebsd.org>; Mon, 23 Apr 2012 20:59:38 +0000 (UTC)
	(envelope-from marcus@freebsd.org)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198])
	by mx1.freebsd.org (Postfix) with ESMTP id 76E088FC16
	for <gnome@freebsd.org>; Mon, 23 Apr 2012 20:59:38 +0000 (UTC)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1])
	by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id
	q3NKxV16017885; Mon, 23 Apr 2012 16:59:31 -0400 (EDT)
Received: from dhcp-64-102-211-16.cisco.com (dhcp-64-102-211-16.cisco.com
	[64.102.211.16])
	by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q3NKxTQ1016831; 
	Mon, 23 Apr 2012 16:59:29 -0400 (EDT)
Message-ID: <4F95C2B1.2050706@freebsd.org>
Date: Mon, 23 Apr 2012 16:59:29 -0400
From: Joe Marcus Clarke <marcus@freebsd.org>
Organization: FreeBSD, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Alexander Leidinger <Alexander@Leidinger.net>
References: <alpine.BSF.2.00.1204222157150.55889@mail.neu.net>
	<CADLFttd0JwjLZyoaVzjWZPE8dNSBptphOooxy6r9VYKuykBXTg@mail.gmail.com>
	<20120423220812.0000178d@unknown>
In-Reply-To: <20120423220812.0000178d@unknown>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Jeremy Messenger <mezz.freebsd@gmail.com>, gnome@freebsd.org,
	AN <andy@neu.net>
Subject: Re: Unable to allocate secure memory from gnome-keyring
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
	<freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 20:59:38 -0000

On 4/23/12 4:08 PM, Alexander Leidinger wrote:
> On Sun, 22 Apr 2012 22:06:41 -0500 Jeremy Messenger
> <mezz.freebsd@gmail.com> wrote:
> 
>> On Sun, Apr 22, 2012 at 9:12 PM, AN <andy@neu.net> wrote:
> 
>>> ** (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.
> 
> I would expect that this is caused by a failed call to mlock(). Only
> root is allowed to do that. I would also expect that this message
> disappears, if the executables is marked as SUID-root. If it makes
> sense to mark it SUID-root from a security point of view in this case or
> not is a different question.

The memory locking message is expected for this very reason.  You can't
suid gnome-keyring-daemon since that will break due to GNOME.  The error
is not fatal, though.

Joe

> 
> Bye,
> Alexander.
> 


-- 
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome