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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=qbrqAkVT3ichRFeA
	gI6aG3uX7nmFYNe+DgZWsz/oWaXiLO4wZFjlmVLzPIylYiUREtRXMC80R7uaAnRs
	Q9NJfslfsGc9gRgPRdotDIVefrbziXxSRfegm2yMZWMzuQkXIZ2SQn/Sz+Ay5Niu
	emx87ArhzqvuB6s6eTDPy2ijEhA=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=4kAoXSSdDaoS2wzA6lzB/v
	Z/3iU=; b=rRYgN2MLFPnYS2ptnLRP4flxY6UgBXzXEOC2mE7Q1QEchsA2blldAm
	ZALnBt6Eo9f3UD9Ssl7SQSqhw/imkAlE+jYEuu9L/hKDf2hLXUDGwQU1NMjg279i
	U0Q7hur2WzY3wCdSNARAS0qGgH2DR3HYQKtsOrur7ZS3/chqhV4l4=
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=2.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=porter!, Porter!, H*MI:sk:57EB444, H*MI:sk:57ECA90
X-HELO: forward1p.cmail.yandex.net
Authentication-Results: smtp1p.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status: 1 0,1 0
Date: Thu, 29 Sep 2016 23:34:14 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1614136129.20160929233414@yandex.ru>
To: Wayne Porter <wporter82 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Unknown+User Unix_Group+505 on smb shares in a domian
In-Reply-To: <20160929184039.GD12532@hdmetxxxx33004g.AD.UCSD.EDU>
References: <57EB4449 DOT 7010206 AT tlinx DOT org>   <20160928180456 DOT GA1128 AT hdmetxxxx33004g DOT AD DOT UCSD DOT EDU>  <57ECA908 DOT 9010402 AT tlinx DOT org>  <20160929184039 DOT GD12532 AT hdmetxxxx33004g DOT AD DOT UCSD DOT EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Wayne Porter!

>>       Essentially you have a bunch of users on different machines that aren't
>> sharing their files under any common (or shared) security authority
>> (like a single domain).  Until you persuade the owners of those linux machines
>> to move the linux machines under a common security authority (like a windows
>> domain) and moving the user accounts into the domain.  Each local account
>> would have to be moved to a domain account with the files under each
>> machine-local account being moved (or "chown'ed") to the new, corresponding
>> domain account).

> The shares are mapped and working just fine in Windows. To IT, there isn't
> anything that needs to be done.

If they really believe that, they are even less qualified than I've thought.
The whole thing works by a pure accident. And a slightest change in
conventions or default behavior of either Windows or Samba may bring the end
to the happy dreams of your IT dep.

> It just happens that Cygwin, which I'm the only one using, maps the Windows
> mapped drives to an unknown user account and makes using it difficult.

Windows maps it to an unknown user account also.
It just happens to know, from which server the account came and can fetch the
names in a subrequest. But they are NOT domain names, neither their UID's are
domain UID's. You can't even control permissions from domain, you'd need to
login to the machine and fiddle with perms locally.

>>       This is an organizational problem that has nothing to do with
>> cygwin, but whether windows and linux machines are using domain or machine-local
>> security.  Until your linux machines and their local user become part of the
>> domain, you can't expect any "write" privileges granted to you under the
>> domain to work on the linux machines.
>> 

> I have write permissions on those machines from Windows. Cygwin thinks I don't so
> files are opened in read-only mode but when I force them to be written, it works.
> I'm not sure if maybe I left this out of my initial information, but these are
> shares that are mapped in Windows on login and there are no issues there, but once
> I open Cygwin, I don't appear to have write access even though I do.

> When mapping the drives in Windows, a username and password are given. Is there no
> way to let Cygwin know about that username without joining the servers to the domain?
> I know that this setup isn't ideal, which is why I'm trying to find a work-around.

I've had this same setup for years, and one unlucky friday, it blew in my face
when I was committing an important batch of change in my project to the
repository.
I've spent next two weeks salvaging the working copy. But nothing worked until
I said "fuck it" and finally took my time to reinstall 64-bit OS and setup a
domain (this is my home network, so I though with only me using it there's no
pressing... guess there was).


-- 
With best regards,
Andrey Repin
Thursday, September 29, 2016 23:26:04

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