X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:from:content-type
	:in-reply-to:message-id:date:to:content-transfer-encoding
	:mime-version; q=dns; s=default; b=M2DttPqGgpEVFxkwKqBsePLds9T6o
	XGfWbLaWJvZVfE9HmUdadll7pUTF0mw1vOGpJ1MclGZL7F+lKD1DLtQGF7HI1FhV
	TvhdJuAe8FWBBPsOWfxXf2T0yt8QcVyNfIg7D8xppCotBh3XyrpVcJV8pkpNQM5N
	wbwx/+WAkZCsmw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:from:content-type
	:in-reply-to:message-id:date:to:content-transfer-encoding
	:mime-version; s=default; bh=jLM2yIDgWpi6IdszVsPaxBPIrrw=; b=wFV
	pfUs0aaHkR35uwIObpIch0JAP/gICkAhu0stvDtEl44DLXJXLmRCPOGoTnUdubQJ
	1462NGxxC0sWhWnabjg6F7SUktByj4KUcAdHwgqw6kWd1OKmHYo249t1c8kSVRK0
	T0qBRibdqniw/YJy9pIDolOPP2IkSyYpbiJmlIH0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: nskntmtas02p.mx.bigpond.com
X-Authentication-Info: Submitted using ID max DOT rockliff AT bigpond DOT com
X-Authority-Analysis: v=2.0 cv=D6DF24tj c=1 sm=1 a=6VslrNzXsdlmF2QCmrgadw==:17 a=kj9zAlcOel0A:10 a=1IlZJK9HAAAA:8 a=w_pzkKWiAAAA:8 a=cgRj0LbuNFJjsd4cTsEA:9 a=CjuIK1q_8ugA:10 a=6VslrNzXsdlmF2QCmrgadw==:117
Subject: Re: Non-privileged use can't logon
References: <003601d05be4$d2574470$7705cd50$@rockliff AT bigpond DOT com> <20150311111729 DOT GW5732 AT calimero DOT vinschen DOT de> <004e01d05bf1$2897d730$79c78590$@rockliff AT bigpond DOT com> <20150311120705 DOT GX5732 AT calimero DOT vinschen DOT de> <005d01d05bf8$8104b210$830e1630$@rockliff AT bigpond DOT com> <20150311125007 DOT GC5732 AT calimero DOT vinschen DOT de>
From: "max DOT rockliff AT bigpond DOT com" <max DOT rockliff AT bigpond DOT com>
Content-Type: text/plain;	charset=us-ascii
In-Reply-To: <20150311125007.GC5732@calimero.vinschen.de>
Message-Id: <E5D47B0F-8F43-45E6-AD14-E648F6675724@bigpond.com>
Date: Wed, 11 Mar 2015 22:25:28 +0800
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Mime-Version: 1.0 (1.0)
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t2BEPnPf020448

Aha! So what you're saying is that in all likelihood the old version I was running didn't have this problem because it simply didn't try to use the windows environment hence no reference to userenv. However some time in the past couple of years this functionality was introduced and I get the error.. Could be a backwards compatibility issue as I'm running it on vista whereas Georg said yesterday that he'd upgraded Cygwin on Win8 and didn't experience the same problem with non-privileged accounts.  Interesting but! I'm working and for that I am grateful :)

I heard you say this type of error had been a problem on and off but with other dlls. Maybe there's a fundamental compatibility issue or maybe a calling convention in the APIs or function definitions from time to time in different Windows versions. .....Just maybe. 

Max

> On 11 Mar 2015, at 8:50 pm, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> 
> Please, https://cygwin.com/acronyms/#TOFU
> 
> Thank you.
> 
> On Mar 11 20:40, Max Rockliff wrote:
>>>> Any ideas?
>>> 
>>> Depends.  As for the actual cause why userenv.dll refuses to load, no.
>>> It's just a simple LoadLibrary call, nothing fancy.  I just tried the
>>> same scenario on my local 8.1 test machine and logging in with an
>>> unprivileged account worked fine.
>>> 
>>> I tried to come up with a workaround for the problem, though.  I just
>>> uploaded a new developer snapshot to https://cygwin.com/snapshots/
>>> 
>>> Just fetch the latest 32 bit cygwin1.dll,
>>> http://cygwin.com/snapshots/x86/cygwin1-20150311.dll.xz
>>> 
>>> Unxz it, chmod +x it.  Stop all Cygwin processes.  In Windows
>>> Explorer, open the C:\cygwin\bin directory.  Rename the original
>>> cygwin1.dll to cygwin1.dll.ORIG.  Move the new cygwin1-20150311.dll
>>> into place and rename it to cygwin1.dll.  Retry your scenario.  And
>>> please report back.
>> 
>> Hey Corinna,
>> 
>> You're a magician.  It seems to have fixed the problem, or at least provided an effective workaround.  Here's a transcript (kinda)
>> 
>> 1.  Downloaded the new cygwin1-20150311.dll.xz  (PS. Kudos for using a
>> yyyymmdd format in the name - I always do, but so many don't
>> 2.  Copied the xz file to my privileged user account home folder and
>> Unxz'ed it.
>> 3.  Used Windows to copy the file cygwin1-20150311.dll to the
>> C:\cygwin\bin folder
>> 4.  Stopped the SSHD service
>> 5.  Renamed the old cygwin1.dll to cygwin1.dll.old
>> 6.  Renamed cygwin1-20150311.dll to cygwin1.dll
>> 7.  Started the SSHD service
>> 8.  Started the terminal
>> 9.  Executed ssh st AT localhost and it logged on successfully no errors.
>>    Max AT Max-PC /bin
>>    $ ssh st AT localhost
>>    st AT localhost's password:
>>    Last login: Wed Mar 11 20:32:00 2015 from ::1
>> 
>>    st AT Max-PC ~
>>    $
>> 10.  And, as we like to say in Australia - Sweet!
>> 
>> What on earth did you change that made the error go away?
> 
> You don't want to know.
> .
> [spoiler alert]
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> I made loading userenv.dll non-fatal in this specific case.  The result
> is that, in scenarios like yours, the user's Windows environment won't
> be merged into the environment of the user's shell started from sshd.
> However, since that's a new functionality anyway, you're not worse off
> than with earlier Cygwin versions.
> 
> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 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