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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=FxdjiL5dqi/eZtT6 YRuuc9jcoPSIe+DomdG+JJW0PTu6f49d1GvctaLLp/9bk3GZfIPVTpvum5t1QReu 5Gy4vWz5PQ1fKLhqBLhhKy72Is3YEvri81w37Udxf+BVUEYsKHeZsgL5Jr/ziRZw uAHSujP80CkBnpVS1krVfauqdbw= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=veuL28tj6XkDp+ywvTgfxQ DPNo8=; b=UWuO1zZ1ulbt5m+8uaEi9h3Lstlr/SrXPs4e492ghkplozKQ1VupGB Uom4MKAqGZ18qOFwe+mMDSz5bCmSGo4FkkPSXu4MnYDP+m0o/AbK66GlD9DuR4MQ TEFQmGGjW60UnI7W+vseXMjOVMFNdeY3pXmfUytQQccVoEnfTuVps= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-4.1 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,UNSUBSCRIBE_BODY autolearn=ham version=3.3.2 spammy=UD:faq.html, faq.html, faqhtml, (unknown) X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=UpATD64B c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=utwiP5Xgel36gtms3kYA:9 a=QEXdDO2ut3YA:10 a=OO2XiV6ZNdAA:10 a=daI9ojH3vpgA:10 a=sRI3_1zDfAgwuvI8zelB:22 Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Accessing SMB share as wrong user? To: cygwin AT cygwin DOT com References: <7f4eb950-de06-2981-c9b4-fd345c11ffb3 AT dd-b DOT net> <940871db-07d8-6528-bef3-f2630a89c505 AT SystematicSw DOT ab DOT ca> <704def19-dfa4-1ebc-512e-fae23199f7a6 AT dd-b DOT net> From: Brian Inglis Message-ID: Date: Mon, 29 May 2017 21:49:52 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <704def19-dfa4-1ebc-512e-fae23199f7a6@dd-b.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfO9umSSCkWPxt9+w+P3DPImyAuN+WP4L4/vqbn0F/mcMcvFOTOe+qVuxWXOlb1KEfF7OXJYxzkSVmx9kfoi95lrGEQJOCZ47EB7DjJydrLvriDxSJbK5 yH3NRpmU4xh4x9h73nXD3SO7MibfeIrDQi7lxOxjrrwK7j0zCT9yGtAzpmXpUd09rSq4aMThDyv+0g== X-IsSubscribed: yes On 2017-05-29 12:37, David Dyer-Bennet wrote: > On 5/29/2017 12:45, Brian Inglis wrote: >> On 2017-05-29 11:16, David Dyer-Bennet wrote: >>> A simpler case demonstrating this; X0 is a new share (created just >>> for testing this) with no prior history, nothing manually set. >>> (Server is FreeNAS, current version). >>> From the beginning, when it first sees it, it shows the file owners >>> and groups weirdly. >>> And then it's able to create a file and write to it *once*, but >>> can't then append to it??? >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ id >>> uid=197608(David Dyer-Bennet) gid=197121(None) >>> groups=197121(None),197609(Ssh >>> Users),545(Users),4(INTERACTIVE),66049(CONSOLE LOGON),11(Authenticated >>> Users),15(This Organization),113(Local account),66048(LOCAL),262154(NTLM >>> Authentication),401408(Medium Mandatory Level) >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ ls -ld . >>> drwxrwxr-x+ 1 Unknown+User Unix_Group+1001 0 May 29 11:55 . >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ getfacl . >>> # file: . >>> # owner: Unknown+User >>> # group: Unix_Group+1001 >>> user::rwx >>> group::rwx >>> other:r-x >>> default:user::rwx >>> default:group::rwx >>> default:group:Unix_Group+1001:rwx >>> default:mask:rwx >>> default:other:r-x >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ echo something > foobar >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ ls -l foobar >>> ----r--r-- 1 Unknown+User Unix_Group+1001 10 May 29 12:11 foobar >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ getfacl foobar >>> # file: foobar >>> # owner: Unknown+User >>> # group: Unix_Group+1001 >>> user::--- >>> group::r-- >>> other:r-- >>> David Dyer-Bennet AT DDB4 //fsfs/x0 >>> $ echo more >> foobar >>> -bash: foobar: Permission denied >> >> See Cygwin User's Guide section on Switching the user context: >> $ cygstart >> /usr/share/doc/cygwin-2.8.0/html/cygwin-ug-net/ntsec.html#ntsec-setuid-overview >> OR >> $ cygstart https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview > > That appears to be instructions on how to temporarily, in code, act as > another user. My problem is that when I create a Bash shell, it > accesses network drives as the wrong user. It may be possible for me to > write a version of Bash that switches to the right (default) user using > that information, but why is it *necessary*? Local drives are accessed > fine. That is the description of what Cygwin does to emulate a user context for remote access to shares - you may want to set up and try methods 1, 2, and 3 to see what works with your network shares. First step may be to change or remap your userid to one not containing spaces using /etc/passwd; see https://cygwin.com/faq.html#faq.setup.name-with-space then https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-samba -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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