Message-ID: <4F762254.2080600@acm.org>
Date: Fri, 30 Mar 2012 14:15:00 -0700
From: David Rothenberger <daveroth@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: BLODA detection code in latest snapshot
References: <20120227122614.GB31025@calimero.vinschen.de> <4F761CB9.4070905@t-online.de>
In-Reply-To: <4F761CB9.4070905@t-online.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 3/30/2012 1:51 PM, Christian Franke wrote:
> On Feb 27, Corinna Vinschen wrote:
>> I've just uploaded a new snapshot "2012-02-27 12:04:23 UTC".  It
>> contains two code snippets which are supposed to help diagnosing BLODA
>> problems.
>> [...]
>> Of course I'd be interested in your experience with this and in any
>> BLODA message you get by setting CYGWIN=detect_bloda.
> 
> Got this with current "2012-03-30 10:24:55 UTC" snapshot:
> 
> $ svn log https://...
> 
> Potential BLODA detected!  Thread function called outside of Cygwin DLL:
>   C:\Windows\syswow64\CRYPT32.DLL

I link svn against CRYPT32.DLL to use the "windows-cryptoapi" password
store code in the Subversion source. This is used by svn to encrypt
passwords it stores in the filesystem. Without it, the only choices are
"gnome-keyring" and "kwallet", which aren't great for Cygwin.

So, that's where the reference to CRYPT32.DLL comes from.

I do see the same message on my Win7 x64 system, but not on my WinXP 32
system.

-- 
David Rothenberger  ----  daveroth@acm.org

--
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