From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Problem with sshd on WindMill
Date: Wed, 13 Dec 2000 02:39:00 -0000 [thread overview]
Message-ID: <0012131139400J.05746@cygbert> (raw)
In-Reply-To: <003201c064a5$ba9237a0$07a3a318@mn.mediaone.net>
Start sshd with option -d and the ssh with option -v to get lots
of debug output. The below output is not enough to be able to
appraise the situation.
Corinna
On Wednesday 13 December 2000 02:40, CyberZombie wrote:
> I loaded the new OpenSSH as bundled in Cygwin (2.3) and can no longer
> connect
> to a Windows Millenium box running the sshd daemon. Prior to this
> (running 2.1.1p4), I had no problems. What follows is selected
> output from the output
> file C:\CYGWIN_SYSLOG.TXT on the WindMill box after various runs:
>
> Protocol 1 with passwd entry for k02189
> ... : Attempting authentication for k02189.
> ... : Connection closed by 168.135.22.40
>
> Protocol 2 with passwd entry for k02189
> ... : userauth-request for user k02189 service ssh-connection
> method none ... : attempt #1
> ... : Failed none for k02189 from 168.135.22.40 port 2529 ssh2
>
> Protocol 1 WITHOUT passwd entry for k02189
> ... : Attempting authentication for illegal user k02189.
> ... : Connection closed by 168.135.22.40
>
> Protocol 2 WITHOUT passwd entry for k02189
> ... : userauth-request for user k02189 service ssh-connection
> method none ... : attempt #1
> ... : input_userauth_request: illegal user k02189
> ... : Failed none for NOUSER from 168.135.22.40 port 2516 ssh2
>
> This is the (comments and blanks cut) /etc/sshd_config file on the
> WindMill box:
>
> DSAAuthentication yes
> Port 80
> Protocol 2,1
> ListenAddress 0.0.0.0
> ServerKeyBits 768
> LoginGraceTime 600
> KeyRegenerationInterval 3600
> PermitRootLogin yes
> IgnoreRhosts yes
> StrictModes yes
> X11Forwarding no
> X11DisplayOffset 10
> PrintMotd yes
> KeepAlive yes
> SyslogFacility AUTH
> LogLevel DEBUG
> RhostsAuthentication no
> RhostsRSAAuthentication no
> RSAAuthentication yes
> PasswordAuthentication no
> PermitEmptyPasswords no
> CheckMail no
> UseLogin no
>
> Does anyone have an idea what is going wrong?
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-12-13 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 17:40 CyberZombie
2000-12-13 2:39 ` Corinna Vinschen [this message]
2000-12-13 5:31 ` CyberZombie
2000-12-13 5:52 ` Corinna Vinschen
2000-12-13 11:11 Rob_Hannah
2000-12-13 15:19 ` Corinna Vinschen
2000-12-13 16:01 Rob_Hannah
2000-12-14 14:34 Rob_Hannah
2000-12-16 7:35 ` Corinna Vinschen
2000-12-16 11:13 ` CyberZombie
2000-12-16 13:52 ` Corinna Vinschen
2000-12-16 16:34 ` CyberZombie
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=0012131139400J.05746@cygbert \
--to=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).