public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Thu, 23 Apr 2020 08:25:39 -0700	[thread overview]
Message-ID: <958405ee-bb3c-042b-fba9-164a75daa87f@mehconsulting.com> (raw)
In-Reply-To: <5fb8039b-d12c-a382-3055-3fb356fb60cd@gmail.com>

On 4/23/2020 5:51 AM, Marco Atzeri via Cygwin wrote:
> Am 23.04.2020 um 13:54 schrieb Mark Hansen:
>> On 4/21/2020 2:52 PM, Mark Hansen wrote:
>>> On 4/21/2020 8:33 AM, Mark Hansen wrote:
>>>> I have a Windows 10 laptop, on which I installed Cygwin. I always log 
>>>> into the machine using
>>>> my corporate domain account. When I log into the machine from my 
>>>> office, everything Cygwin
>>>> works fine.
>>>>
>>>> When I log into my laptop from home (which I'm working from home for 
>>>> a while now, due to
>>>> COVID-19), I still log in using my corporate domain account, but 
>>>> Cygwin acts differently.
>>>>
>>>> Here is my user id (from the id command) when I log in from the office:
>>>>
>>>> uid=1293438(Mark.Hansen) gid=1049089(Domain Users) ...
>>>>
>>>> Here is the same when I've logged in with the machine at home:
>>>>
>>>> uid=1293438(MAN+User(244862)) gid=1293438
>>>>
>>>> (MAN) is the domain.
>>>>
>>>> The actual problem I'm having is that Cygwin tools like ssh, git, 
>>>> etc. can't find my .ssh
>>>> directory. They are looking in "/" rather than my home directory.
>>>>
>>>> I tried copying my .ssh directory from my home to "/" and although it 
>>>> was created, the
>>>> files have the wrong permissions and I'm unable to change them.
>>>>
>>>> Is there something I can tweak to get Cygwin to understand which user 
>>>> I am so the ssh
>>>> stuff can start working again?
>>>>
>>>> Thanks for any help.
>>>>
>>>
>>> To answer a question posed by someone to my private e-mail:
>>>
>>> I didn't have the HOME environment variable set at first. When the PC 
>>> is at my office,
>>> Cygwin worked fine. When I took the PC home and logged in there, I had 
>>> severe Cygwin
>>> issues - I wasn't able to open a Cygwin Terminal or an XTerm terminal 
>>> - it seemed it
>>> didn't know where my HOME directory was.
>>>
>>> As a result, I set my HOME directory in the environment settings for 
>>> my user. Once I
>>> did that, I was able to use the Cygwin Terminal and XTerm terminals 
>>> again.
>>>
>>> The only thing that is still not working (as far as I can see) is any 
>>> ssh client which
>>> needs to find the .ssh directory (like ssh or git, etc.).
>>>
>> 
>> Assuming Cygwin doesn't know about my user (when the PC is at home) - is 
>> there something
>> I can run to reset what Cygwin thinks is the user?
>> 
>> Otherwise, I'll try reinstalling Cygwin and see if that helps.
>> 
>> -- 
> 
> check the differences in outputs for
> 
>       "mkpasswd -c" and "id"
> 
> in the two cases.
> 
> 
> 

I have the differences for 'id' in the two cases. However, I currently don't have access to
my office during the 'stay at home' order we're having to honor these days.

I don't understand the difference in the 'id' output, but they are different. I showed
the first little bit of each in my first message. Does this help? Should I attach the
complete output of the two runs here?


  reply	other threads:[~2020-04-23 15:25 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 [this message]
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
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=958405ee-bb3c-042b-fba9-164a75daa87f@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).