public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: No way to use ssh ~/.ssh/config with "noacl" option
Date: Sat, 04 Nov 2017 21:20:00 -0000	[thread overview]
Message-ID: <02939a2a-8dee-6c79-fd80-24c9b9073e52@SystematicSw.ab.ca> (raw)
In-Reply-To: <87h8u9ew9n.fsf@Rainer.invalid>

On 2017-11-04 12:25, Achim Gratz wrote:
> Matt D. writes:
>> It's not perfect but I've always had trouble with all of the
>> modifications Cygwin makes to a file's permissions to support
>> POSIX-style ACLs. I do miss being able to manage them with chmod and
>> setfacl though.
> 
> Just remove any ACL inheritance on the home directory before populating
> it (or recursively remove it for an existing directory, but that can be
> more tricky).  I suggest to use a sub-directory of your actual Windows
> home, otherwise you might get into trouble with applications writing dot
> files into it and/or getting confused by the dot files from Cygwin.
> It's easy enough to mount it to /home/$USER so it's where you'd normally
> expect it to show up.

If you remove the DACLs on directories, you will be unable to access any files
without using Cygwin, as Windows sees no permissions, and any files created by
Windows programs will have no Cygwin permissions, and you will be unable to
access those files from Cygwin or Windows programs, without doing manual Windows
security fixups.
I've hit some directories with setfacl -bk, and quickly regretted it.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

  reply	other threads:[~2017-11-04 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04  9:47 Matt D.
2017-11-04 11:37 ` Corinna Vinschen
2017-11-04 11:47   ` Matt D.
2017-11-04 13:31     ` Matt D.
2017-11-04 15:30       ` Matt D.
2017-11-04 15:43         ` Achim Gratz
2017-11-04 17:15           ` Matt D.
2017-11-04 18:25             ` Achim Gratz
2017-11-04 21:20               ` Brian Inglis [this message]
2017-11-04 16:37         ` Corinna Vinschen
2017-11-04 17:22           ` Matt D.
2017-11-04 17:38             ` Matt D.
2017-11-08 23:07               ` Matt D.

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=02939a2a-8dee-6c79-fd80-24c9b9073e52@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).