From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: No way to use ssh ~/.ssh/config with "noacl" option
Date: Sat, 04 Nov 2017 15:43:00 -0000 [thread overview]
Message-ID: <87shdudp76.fsf@Rainer.invalid> (raw)
In-Reply-To: <59FDDCFA.9030306@codespunk.com> (Matt D.'s message of "Sat, 4 Nov 2017 11:30:02 -0400")
Matt D. writes:
> This makes sense because Cygwin is pulling the NTFS permissions as
> there are no Cygwin ACLs defined.
>
> The only workaround is to use Window's Security diaglog to disable
> inherited permissions and remove the Users group. This does seem to
> satisfy things.
That's the correct thing to do, even though you made this unnecessarily
hard for yourself by mounting your home directory with "noacl".
> I suppose the argument now is whether this behavior should change in
> the face of a drive mounted with "noacl". It took a bit of guesswork
> as neither chmod or setfacl was changing the NTFS permissions.
I don't think ssh should use files that are accessible by somebody
else. The noacl mount option is sometimes useful, but certainly not in
this situation, as you found out.
> Interestingly, a config file that I chmodded when the drive was
> mounted with Cygwin ACLs still works with ssh even though "noacl" is
> now defined and it is still part of the HOSTNAME\Users group. Neither
> stat or getfacl show these permissions but they can be seen in the
> security tab of the file properties. I'm guessing that it works
> because it has HOSTNAME\None below HOSTNAME\<my account> or something?
The effective access rights as shown by icacls or similar tools should
tell you what is going on. If the directory is not readable, then the
file is effectively inaccessible I think.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
next prev parent reply other threads:[~2017-11-04 15:43 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 [this message]
2017-11-04 17:15 ` Matt D.
2017-11-04 18:25 ` Achim Gratz
2017-11-04 21:20 ` Brian Inglis
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=87shdudp76.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).