public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: "David Balažic" <xerces9@gmail.com>, cygwin@cygwin.com
Subject: Re: Conflict if same username local and in domain
Date: Fri, 30 Oct 2020 10:29:59 +0300	[thread overview]
Message-ID: <95350468.20201030102959@yandex.ru> (raw)
In-Reply-To: <CAPJ9Yc8QBJT9yAbE6QB1TZGTWtOd8mHkgZ5534ZnnOKs0jh4bg@mail.gmail.com>

Greetings, David Balažic!

> I started Cygwin Terminal to find out, I landed in the other users
> home folder and have no write access.

> What happened was:
>  - log into Windows as domain user DOM\JOE
>  - start cygwin shell, land in /home/joe
>  - log into Windows as local user JOE
>  - start cygwin shell, land in /home/joe , but with no write access,
> as it belongs to other user according to Windows


> Is this a known issue? Should cygwin use a different username?

This is a caveat of the default nsswitch configuration in Cygwin.
It uses home directories inside Cygwin's own directory tree by default and
name them after username without domain, but you can configure it to either
use a different home directory name or just use user's profile as home
directory. Which is, if you ask me, way more logical.

Be aware of the noacl flag for mounting directories outside Cygwin tree, or
you may surprise your Windows applications with less than trivial ACE setups
generated by Cygwin in "strict POSIX" mode.


-- 
With best regards,
Andrey Repin
Friday, October 30, 2020 10:25:49

Sorry for my terrible english...

      parent reply	other threads:[~2020-10-30  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 12:39 David Balažic
2020-10-29 20:42 ` L A Walsh
2020-10-31 10:56   ` David Balažic
2020-11-02  3:45     ` L A Walsh
2020-11-02  6:33     ` Andrey Repin
2020-10-30  7:29 ` Andrey Repin [this message]

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=95350468.20201030102959@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=xerces9@gmail.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).