Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3AB0CBCD.86260F06@bbn.com> Date: Thu, 15 Mar 2001 09:03:57 -0500 From: Wilson Farrell X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin Subject: Re: Odd ssh2 problem References: <045101c0acbf$b4e98df0$1d1587a8 AT deluxe DOT com> <20010314215447 DOT K8866 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > > On Wed, Mar 14, 2001 at 01:48:12PM -0600, CyberZombie wrote: > > I ran into this one awhile ago...I don't see it in > > /usr/doc/Cygwin/openssh-2.5.1p2.README. The problem is that $HOME isn't > > Hmm. You're right. It's not in the README. Actually it's even never > mentioned in the man pages. I will add it to the README in the next > version. Actually, I have found (as mentioned by DJ) that the ssh client ignore $HOME and looks at the passwd file. Ran into this exact problem yesterday. $HOME was set correctly, but the passwd file was botched. Maybe it looks at both? BTW: I had a couple of people in my office do a fresh installation of cygwin and found that it creates passwd file entries for every NT account except the one currently logged in. Hence, they ran into the ssh problem. Is this correct behavior of the initial passwd file creation? Cygwin is great. Thanks for the hard work. wilson -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple