From: Andrey Repin <anrdaemon@yandex.ru>
To: David Dyer-Bennet <dd-b@dd-b.net>, cygwin@cygwin.com
Subject: Re: Accessing SMB share as wrong user?
Date: Mon, 29 May 2017 20:22:00 -0000 [thread overview]
Message-ID: <705418614.20170529225346@yandex.ru> (raw)
In-Reply-To: <7f4eb950-de06-2981-c9b4-fd345c11ffb3@dd-b.net>
Greetings, David Dyer-Bennet!
> All my files are on drive P: in Windows, which is an SMB share
> equivalent to \\fsfs\ddb\Documents. Everything works fine in windows
> apps, and I see what I expect in Explorer, including when I go down to
> security properties and look in detail.
> However, Cygwin has trouble with this lately (I can't trace exactly when
> it started happening; not weeks, maybe a year, but I've been running
> essentially this way since 2006 and most of the time things were fine).
> Cygwin appears to be accessing the share as some kind of unknown user,
> rather than as the proper user configured in Windows for that share
> (which is FSFS\ddb).
> In Cygwin "id" shows
> $ id
> uid=197608(David Dyer-Bennet) gid=197121(None)
> groups=197121(None),
> 114(Local account and member of Administrators group),
> 544(Administrators),
You're running Cygwin with elevated privileges.
> 545(Users),4(INTERACTIVE),66049(CONSOLE
> LOGON),11(Authenticated Users),15(This Organization),113(Local
> account),66048(LOCAL),262154(NTLM Authentication),405504(High Mandatory
> Level)
> but if I create a file it gets created owned by "Unknown+User":
> $ touch foobar
> David Dyer-Bennet@DDB4 /cygdrive/p
> $ ls -l foobar
> ----r--r-- 1 Unknown+User Unix_Group+1001 0 May 28 17:27 foobar
> David Dyer-Bennet@DDB4 /cygdrive/p
> $ getfacl foobar
> # file: foobar
> # owner: Unknown+User
> # group: Unix_Group+1001
Your share is located on Samba server.
> user::---
> group::r--
> other:r--
> And then of course I can't access it:
> $ echo things >> foobar
> -bash: foobar: Permission denied
See Cygwin manual about setting up your network identity.
Read around nsswitch.conf and implications of its different settings.
> I haven't that I've noticed done anything to change what user I run as;
> $USER is "David Dyer-Bennet" (the Windows username I'm in under), and
> /etc/passwd has default output from mkpasswd,
Ditch /etc/passwd unless you absolutely require it.
> including the user "David
> Dyer-Bennet" with the UID 197608 (same is ID shows at the command line).
> At least I can count on people here not answering "just ditch
> Cygwin"...right?
And please leave ramblings outside the list. This was absolutely uncalled for.
--
With best regards,
Andrey Repin
Monday, May 29, 2017 22:49:56
Sorry for my terrible english...
--
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 20:05 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
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 [this message]
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=705418614.20170529225346@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=dd-b@dd-b.net \
/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).