From: David Dyer-Bennet <dd-b@dd-b.net>
To: cygwin@cygwin.com
Subject: Re: Accessing SMB share as wrong user?
Date: Mon, 29 May 2017 19:43:00 -0000 [thread overview]
Message-ID: <704def19-dfa4-1ebc-512e-fae23199f7a6@dd-b.net> (raw)
In-Reply-To: <940871db-07d8-6528-bef3-f2630a89c505@SystematicSw.ab.ca>
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@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@DDB4 //fsfs/x0
>> $ ls -ld .
>> drwxrwxr-x+ 1 Unknown+User Unix_Group+1001 0 May 29 11:55 .
>> David Dyer-Bennet@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@DDB4 //fsfs/x0
>> David Dyer-Bennet@DDB4 //fsfs/x0
>> David Dyer-Bennet@DDB4 //fsfs/x0
>> $ echo something > foobar
>> David Dyer-Bennet@DDB4 //fsfs/x0
>> $ ls -l foobar
>> ----r--r-- 1 Unknown+User Unix_Group+1001 10 May 29 12:11 foobar
>> David Dyer-Bennet@DDB4 //fsfs/x0
>> $ getfacl foobar
>> # file: foobar
>> # owner: Unknown+User
>> # group: Unix_Group+1001
>> user::---
>> group::r--
>> other:r--
>> David Dyer-Bennet@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.
--
David Dyer-Bennet <dd-b@dd-b.net>
http://dd-b.net/
--
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
next prev parent reply other threads:[~2017-05-29 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 3:12 David Dyer-Bennet
2017-05-29 18:37 ` David Dyer-Bennet
2017-05-29 19:18 ` Brian Inglis
2017-05-29 19:43 ` David Dyer-Bennet [this message]
2017-05-30 5:58 ` Brian Inglis
2017-05-30 7:39 ` David Dyer-Bennet
2017-05-30 8:21 ` Brian Inglis
2017-05-30 16:47 ` Andrey Repin
2017-05-29 20:22 ` Andrey Repin
2017-05-29 21:30 ` David Dyer-Bennet
2017-05-30 4:14 ` David Dyer-Bennet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=704def19-dfa4-1ebc-512e-fae23199f7a6@dd-b.net \
--to=dd-b@dd-b.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).