From: "Matt D." <matt@codespunk.com>
To: cygwin@cygwin.com
Subject: No way to use ssh ~/.ssh/config with "noacl" option
Date: Sat, 04 Nov 2017 09:47:00 -0000 [thread overview]
Message-ID: <59FD8C99.8010703@gmail.com> (raw)
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate to request ssh to ignore this requirement when
"noacl" present on the mounted volume?
Matt D.
--
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 reply other threads:[~2017-11-04 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 9:47 Matt D. [this message]
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
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=59FD8C99.8010703@gmail.com \
--to=matt@codespunk.com \
--cc=codespunk+cygwin@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).