public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wayne Porter <wporter82@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Unknown+User Unix_Group+505 on smb shares in a domian
Date: Sun, 02 Oct 2016 23:58:00 -0000	[thread overview]
Message-ID: <20161002234944.vywfzlwv3lwiaqof@Chronos> (raw)
In-Reply-To: <57F199B9.5010000@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]

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 something I can set in
> > my local /etc/passwd to convince Cygwin to map it to my user account?
> ---
> 	Let me phrase this differently.
> 
> 	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.

> 
> 	The Domain is a means to provide common trusted access to a group
> of people who have agreed to honor each others' permission settings.  Right
> now, the linux people are not in a common-trust group, so you can't force
> your wanted access upon them.
> 
> 	Until you and their machines share a common security token (the Domain
> token), you can't have shared permission settings.
> 
> 	Alternatively , you might be able to convince the linux people to
> give you an account on each linux machine, and use that login when attaching
> 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 domain,
> you can't force your desired access upon them.
> 

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!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-10-02 23:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 23:59 Wayne Porter
2016-09-28 17:55 ` Linda Walsh
2016-09-28 19:52   ` Wayne Porter
2016-09-28 21:44     ` Andrey Repin
2016-09-28 22:59       ` Wayne Porter
2016-09-29 20:35         ` Andrey Repin
2016-09-29  8:38     ` Linda Walsh
2016-09-29 19:35       ` Wayne Porter
2016-09-30  5:05         ` Andrey Repin
2016-10-01 22:38           ` Wayne Porter
2016-10-02 23:49         ` Linda Walsh
2016-10-03  1:28           ` Wayne Porter
2016-10-02 23:44     ` Linda Walsh
2016-10-02 23:58       ` Wayne Porter [this message]
2016-10-03  6:33         ` Linda Walsh
2016-09-29 15:22 Roland Schwingel
2016-10-19 11:45 ` Corinna Vinschen

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=20161002234944.vywfzlwv3lwiaqof@Chronos \
    --to=wporter82@gmail.com \
    --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).