From: Mark Hansen <cygwin@mehconsulting.com>
To: cygwin@cygwin.com
Subject: Re: Problems with ssh when I log into my PC using my corporate domain while working from home
Date: Fri, 24 Apr 2020 06:43:13 -0700 [thread overview]
Message-ID: <8ed7fa18-f3f5-696b-c875-7210ed96426f@mehconsulting.com> (raw)
In-Reply-To: <e2524361-e748-e1fa-5df3-3a4ed4aea8e8@huarp.harvard.edu>
On 4/23/2020 11:57 AM, Norton Allen wrote:
>
> I also have had to deal with this problem. You should certainly read
> https://cygwin.com/cygwin-ug-net/ntsec.html.
>
> After much experimenting and consultation with Corinna, we decided the
> best solution for me was:
>
> * Create /etc/passwd and /etc/group files
> o For /etc/passwd, I included just my account, and I actually
> editted it further to use my preferred username (rather than my
> domain username) and my correct home directory
> * Edit /etc/nsswitch.conf with:
> o passwd: files
> o group: files
>
> This is not the generally recommended configuration, but in the
> situation where you cannot reach the domain server, it may be the best
> alternative. You may or may not need to back these changes out when you
> are back at work. I have not had a problem at work, but we are only
> loosely connected to the domain, so YMMV.
>
This solved the issue for me. After doing what was suggested, above, I killed all the
Cygwin processes (actually, I rebooted the machine) and now when I try to perform
commands like ssh and git (which need to access files in my .ssh directory) they
are able to find the files and therefore are working again.
I realize that when I am able to once again work from my office, I may need to undo
these changes, but I'm quite happy that at least for now, it's working again.
Thanks to all who helped with this!
next prev parent reply other threads:[~2020-04-24 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 15:33 Mark Hansen
2020-04-21 21:52 ` Mark Hansen
2020-04-23 11:54 ` Mark Hansen
2020-04-23 12:51 ` Marco Atzeri
2020-04-23 15:25 ` Mark Hansen
2020-04-23 19:19 ` Marco Atzeri
2020-04-23 19:30 ` Marco Atzeri
2020-04-23 21:50 ` Mark Hansen
2020-04-24 5:11 ` Brian Inglis
2020-04-23 17:26 ` ASSI
2020-04-23 18:10 ` Mark Hansen
2020-04-23 18:57 ` Norton Allen
2020-04-24 13:43 ` Mark Hansen [this message]
2020-04-23 19:33 ` Achim Gratz
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=8ed7fa18-f3f5-696b-c875-7210ed96426f@mehconsulting.com \
--to=cygwin@mehconsulting.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).