DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=GeHDdbAOhEBzsO5HobT15+4W+QeZdExS4UMqtp2WfNK
	aT2cjof8yS0ewxYRYGriyrpYX1YRj9CPvvx1ZUthy1zMEBmHiTilVf1IMWrAAQNE
	AFXJML7olZ77v4mv0oYKT2aOGzmTgQY/K/SdkyjO59T6nsOzyDqCYjQd8MbtsbSs
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <52526B2A.1080603@asperasoft.com>
Date: Mon, 07 Oct 2013 10:04:58 +0200
From: gaillard <gaillard AT asperasoft DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Re: second exec channel cannot access windows share (open-ssh)
References: <524EF7EC DOT 8040204 AT cygwin DOT com>
In-Reply-To: <524EF7EC.8040204@cygwin.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Thanks. Yes there are passwords on shares.

What confuses me is that it works on the first invocation of exec channel.
Is there any reason why it works then ?

On 10/4/2013 7:16 PM, Larry Hall (Cygwin) wrote:
> On 10/4/2013 3:26 AM, gaillard wrote:
>> Hi,
>>
>> My company uses cygwin to enable client users to access an application through
>> open-ssh server via an ssh exec-channel. After the session connects fine, the
>> firstly created exec channel is able to access the mounted shares installed on
>> the box (in my test a Windows Server 2008 R2).
>> The issue comes when opening the second exec channel that is not able to access
>> the shares.
>>
>>  From the tests I made the second channel is not impersonating the user
>> correctly
>> since it happears the application process runs as "Local System" which would
>> explain the issue.
>>
>> The open-ssh service is installed under a special user account that runs
>> with the
>> following settings in local security policy:
>> - adjust memory quotas for a process
>> - create a token object
>> - logon as a service
>> - replace a process level token
>>
>> I tried to add this but without success:
>> - impersonate a client after authentication
>>
>> I've also read the doc "Using Windows Security in Cygwin" but I'm unsure of the
>> correct diagnostic for the problem: wrong setting (do I need to use LSA
>> authentication)
>> or is it a bug?
>>
>> Any advice will be appreciated.
>
> If you have passwords on your shares (and it sounds like you do), then
> your only real altrernative is the third option as described in the
> Users Guide:
>
> <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3>
>
>

-- 
Gilles Gaillard


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