From: greenspan <daniel.greenspan@jhuapl.edu>
To: cygwin@cygwin.com
Subject: Re: ssh logon failure
Date: Wed, 13 Nov 2013 04:16:00 -0000 [thread overview]
Message-ID: <1384316180166-104282.post@n5.nabble.com> (raw)
In-Reply-To: <52817C34.2080501@cygwin.com>
I feel like a terrier peeling away an onion. Darn it, this is going to work!
I agree with your comment about being in the weeds and started over, in the
process discovering why HOME was set improperly (using the domain switch for
mkpasswd instead of local). I reinstalled ssh, re-ran ssh-host-config, and
now am in this situation: I can ssh in, but only using public key
authentication. Passwords do not work (and they must for this application).
When I use a password, the login process seems like it's working - I see the
MOTD, but am immediately disconnected. The server logs simply state that
the client disconnected. The client -vvv option shows this (everything
before MOTD not shown):
-I have tried temporarily removing my .bashrc, .profile and so on, but this
does not change the issue.
-.ssh is owned by me and is mode 700; all .ssh contents are owned by me and
are mode 600
-I've issued "chmod 600 /etc/ssh*"
-I've manually examined all binaries in /bin, /usr/bin, and /usr/sbin to
verify that they have reasonable modes and owners (all are owned by me (an
administrative user), and all are mode 755)
-I own my directory in /home and it has mode 755
-I am not using PAM
-Passwords are not turned off in /etc/sshd_config
Attached is the output of cygcheck.
cygcheck.txt <http://cygwin.1069669.n5.nabble.com/file/n104282/cygcheck.txt>
--
View this message in context: http://cygwin.1069669.n5.nabble.com/ssh-logon-failure-tp57002p104282.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
prev parent reply other threads:[~2013-11-13 4:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 7:04 marco atzeri
2012-06-06 8:37 ` Corinna Vinschen
2012-06-11 19:52 ` marco atzeri
2012-06-21 8:08 ` marco atzeri
2012-06-21 9:11 ` Corinna Vinschen
2012-08-13 6:03 ` thebardingreen
2012-08-14 14:15 ` marco atzeri
2012-06-07 8:55 ` DakMark
2012-06-07 10:02 ` marco atzeri
2013-08-07 17:15 ` Yuki Ishibashi
2013-08-07 17:34 ` Larry Hall (Cygwin)
2013-10-25 2:04 ` Dan Greenspan
2013-10-25 2:30 ` Larry Hall (Cygwin)
2013-11-11 23:48 ` greenspan
2013-11-12 14:32 ` George Demmy
2013-11-12 0:23 ` greenspan
2013-11-12 0:54 ` Larry Hall (Cygwin)
2013-11-13 4:16 ` greenspan [this message]
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=1384316180166-104282.post@n5.nabble.com \
--to=daniel.greenspan@jhuapl.edu \
--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).