From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8013 invoked by alias); 3 Dec 2011 23:04:46 -0000 Received: (qmail 7937 invoked by uid 22791); 3 Dec 2011 23:04:24 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Sat, 03 Dec 2011 23:04:11 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 7F3A82C01F7; Sun, 4 Dec 2011 00:04:08 +0100 (CET) Date: Sat, 03 Dec 2011 23:04:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: gnome-keyring bug in snapshots Message-ID: <20111203230408.GC12518@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20111203184459.GA21371@ednor.casa.cgf.cx> <20111203213047.GA24925@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20111203213047.GA24925@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-12/txt/msg00053.txt.bz2 On Dec 3 16:30, Christopher Faylor wrote: > On Sat, Dec 03, 2011 at 01:44:59PM -0500, Christopher Faylor wrote: > >On Tue, Nov 29, 2011 at 09:19:10PM -0600, Yaakov (Cygwin/X) wrote: > >>For some time now, snapshots have displayed a bug wrt gnome-keyring, > >>namely that passwords don't "register" when entered. This wreaks > >>havoc on the GNOME desktop where so many programs rely on > >>gnome-keyring. > >>[...] > According to strace, the "couldn't allocate secure memory..." messages > seems to be caused by this: > > gnome-keyring-daemon 3820 seterrno_from_nt_status: /cygnus/src/uberbaum/winsup/cygwin/mmap.cc:1399 status 0xC0000061 > > That is coming from mlock() which hasn't changed in months. > > The status above translates to: STATUS_PRIVILEGE_NOT_HELD and that is > coming from NtLockVirtualMemory() . > > Yaakov or Corinna does any of the above mean anything to you? As documented in mmap.cc, mlock functionality requires the SE_LOCK_MEMORY privilege which only the SYSTEM account holds by default. Mlock is unchanged since it has been introduced in 2005. Having said that, after searching the net for a while I found out that the privilege requirement is excessive. In 2005 I stumbled over the wrong interpretation of what the VirtualLock function is doing. Not even Microsoft guys are immune to that(*), apparently. I dropped the requirement for the SE_LOCK_MEMORY privilege in CVS so every process should be able to call mlock successfully now. Corinna (*) http://blogs.msdn.com/b/oldnewthing/archive/2007/11/06/5924058.aspx See the last paragraph. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple