From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17328 invoked by alias); 2 Oct 2016 23:49:51 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 17312 invoked by uid 89); 2 Oct 2016 23:49:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.6 required=5.0 tests=AWL,BAYES_40,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,TBC,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 spammy=Until, user-names, attaching, commontrust X-HELO: mail-pa0-f46.google.com Received: from mail-pa0-f46.google.com (HELO mail-pa0-f46.google.com) (209.85.220.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 02 Oct 2016 23:49:48 +0000 Received: by mail-pa0-f46.google.com with SMTP id qn7so55021340pac.3 for ; Sun, 02 Oct 2016 16:49:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=k6WySWSENCmi4bfRc/AS1sz9IldAQ+ttTN96A3Rtvcw=; b=GqqDEeOsMNXhmdI0VLomkYqvkqAB8AXZ/n1HfovyR0PFgd93eEKk67WPo3NOowK/Sw eMyFS0NkdZutQCnkyeU111g2eRB94Ebimb1jXHzFRaReZbWhpMv/oTEM7EeX3JKBDTB9 0aXesOUL0jpNOgNYm5ajJkQDGw7Jg18NiuHUSd/E/VOXpbQvYhfPf4YoDqsXVwTViAGx uWYmrUKgn3Gj+4za34D0/msMxbrydW0JQtoH1dBECgoVSuauVmKeafi3tyzec2Y4O/aG gTd9gkVPCWX0aS4ZXsKW8XdNZYFuT90oHUfcDLCNMbm4DEt3kRAE7PkZQI7/zRllVrwv yx4Q== X-Gm-Message-State: AA6/9RlgiEse1Bdao2eO4sUdlYjm6JgPrtxEeK0ZoMv/tLPOFYk+zFMuFzW/g+tRfWWUAw== X-Received: by 10.66.10.170 with SMTP id j10mr32374008pab.3.1475452187202; Sun, 02 Oct 2016 16:49:47 -0700 (PDT) Received: from Chronos (ip68-107-32-241.sd.sd.cox.net. [68.107.32.241]) by smtp.gmail.com with ESMTPSA id k69sm42257840pfb.85.2016.10.02.16.49.46 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 02 Oct 2016 16:49:46 -0700 (PDT) Date: Sun, 02 Oct 2016 23:58:00 -0000 From: Wayne Porter To: cygwin@cygwin.com Subject: Re: Unknown+User Unix_Group+505 on smb shares in a domian Message-ID: <20161002234944.vywfzlwv3lwiaqof@Chronos> References: <57EB4449.7010206@tlinx.org> <20160928180456.GA1128@hdmetxxxx33004g.AD.UCSD.EDU> <57F199B9.5010000@tlinx.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iebja2oufvefviln" Content-Disposition: inline In-Reply-To: <57F199B9.5010000@tlinx.org> User-Agent: NeoMutt/20160910 (1.7.0) X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00031.txt.bz2 --iebja2oufvefviln Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2466 On Sun, Oct 02, 2016 at 04:35:21PM -0700, Linda Walsh wrote: > Wayne Porter wrote: > > The server that the W: drive is mapped on is not using domain accounts.= As far as I know, > > all Linux servers we have are running local accounts. Is there somethin= g I can set in > > my local /etc/passwd to convince Cygwin to map it to my user account? > --- > Let me phrase this differently. >=20 > The linux accounts that are not in your domain and are under > private user-names, are NOT something that you have "write" permission to. > It sounds like those users (users outside your domain -- and not within > your administrative group) have allowed "anyone" to have read access, but > it makes sense that they wouldn't trust "anonymous" (that's you, if you > haven't authenticated against their machine). You seem to be asking > for access to files owned by people outside your group (or maybe outside > your company, for that matter, it's not known). This is correct, the linux machines have local accounts that I have mapped to drive letters in Windows. They are my accounts set up with my username and password and I have full read/write access to the folders in question. Cygwin just thinks I have read-only access and when I attempt to write to the files, I can. >=20 > The Domain is a means to provide common trusted access to a group > of people who have agreed to honor each others' permission settings. Rig= ht > now, the linux people are not in a common-trust group, so you can't force > your wanted access upon them. >=20 > Until you and their machines share a common security token (the Domain > token), you can't have shared permission settings. >=20 > Alternatively , you might be able to convince the linux people to > give you an account on each linux machine, and use that login when attach= ing > to a share on that linux machine -- but that would be a pain. Certainly, > if they agreed to use a common domain and shared things with other domain > users, that would be easier, but until they agree to be in a common domai= n, > you can't force your desired access upon them. >=20 This is how it is currently set up. I can log in to the server via ssh or use the current method, which is to map the network share using my account credentials that they have set up for me. This works just fine in Windows and for the most part in Cygwin. I can read/write from the files but vim opens all files in read-only mode and I have to save using :w! --iebja2oufvefviln Content-Type: application/pgp-signature; name="signature.asc" Content-length: 473 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJX8Z0QAAoJEMcDZgYHTWDO6tUH/2toSw/ysglFiXMEslcfusKm Va6Y7D3ZX4nQrewYzEzdOddNSGMyfXHRsZRzIvOMBSacZL+2REyZZ5Dtoad3IYu+ rx2zmypzqRrTEfb0/U6sHoclCQ2wYss91IsLYwci8D1wWKr5YKO/uKsuFBhar+FV 90CS/GyjZJ7TUcjtjhKoqPwiZnflvsUxNEzUfTg+/0FOPdxRyquCiEqld3V8bAYW wmGu/nByfBux32ttTexcl4i95JuOJT7nWBxNSoWmYksX/DWjXFqAJUBUiinLpyhK XEA0iP49Iklv6CZ1zRfr/iK9tp3ckMpIKW5iRgOHTxGmWWMTpH+tKM68eRsnlJc= =5ndz -----END PGP SIGNATURE----- --iebja2oufvefviln--