This is the mail archive of the
mailing list for the Cygwin project.
Re: ssh logon failure
- From: George Demmy <gdemmy at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 12 Nov 2013 09:32:02 -0500
- Subject: Re: ssh logon failure
- Authentication-results: sourceware.org; auth=none
- References: <4FCF00EB dot 2070600 at gmail dot com> <loom dot 20120607T103956-836 at post dot gmane dot org> <4FD07C1D dot 5070909 at gmail dot com> <loom dot 20130807T185544-35 at post dot gmane dot org> <52028508 dot 7000102 at cygwin dot com> <loom dot 20131025T023724-855 at post dot gmane dot org> <5269D1AA dot 5010306 at cygwin dot com> <1384213686304-104251 dot post at n5 dot nabble dot com>
On Mon, Nov 11, 2013 at 6:48 PM, greenspan wrote:
> Larry, thanks for your reply. I am using windows 7. I've tried changing
> ownership of /var/empty to cyg_server, but this doesn't help.
> FYI my "Fix" only worked for a day before failing again. Now I'm back to
> square one.
FWIW I was struggling with setting up ssh on a heterogeneous set of
boxes and all the while I was thinking I had sshd messed up but I
think turned out that the uids on the files in .ssh were inconsistent.
A recursive chown on the .ssh dir and locking the dir/file perms down
to 700/600 solved a heap of problems for me. The one sshd thing that
bit me was DNS, but I set UseDNS no in /etc/sshd_config and cleared
that up as well.
One of the mantras that it helps to repeat is that "ssh on Cygwin
works" so it's
a matter of making sure yourenvironment is right:
- valid uid/USERNAME/HOME in /etc/passwd
- .ssh is in $HOME and chown $USERNAME and chmod 700
- all files in .ssh are chown $USERNAME and chmod 600 (not strictly
necessary, but removes doubt)
- public keys from foreign boxes stashed away properly in .ssh/authorized_keys
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple