public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Rob_Hannah@deluxe.com
To: cygwin@sourceware.cygnus.com
Subject: Re: Problem with sshd on WindMill
Date: Wed, 13 Dec 2000 11:11:00 -0000	[thread overview]
Message-ID: <OF17993F39.DEBF1922-ON862569B4.0068F021@deluxe.com> (raw)

As requested, here is the full output of both "ssh -v" and "sshd -d".  In
order to simplify, I'm only including the output of running via Protocol 1
when no entry exists on the WindMill passwd file for the given user (which
worked in the prior OpenSSH).

ssh -v:
  SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
  Compiled with SSL (0x0090581f).
  debug: Reading configuration data /etc/ssh_config
  debug: Applying options for *
  debug: Applying options for 168.135.21.101
  debug: Seeding random number generator
  debug: ssh_connect: getuid 1003 geteuid 1003 anon 1
  debug: Connecting to 168.135.21.101 [168.135.21.101] port 80.
  debug: Connection established.
  debug: Remote protocol version 1.99, remote software version OpenSSH_2.3.0p1
  debug: no match: OpenSSH_2.3.0p1
  debug: Local version string SSH-1.5-OpenSSH_2.3.0p1
  debug: Waiting for server public key.
  debug: Received server public key (768 bits) and host key (1024 bits).
  debug: Host '168.135.21.101' is known and matches the RSA host key.
  debug: Seeding random number generator
  debug: Encryption type: 3des
  debug: Sent encrypted session key.
  debug: Installing crc compensation attack detector.
  debug: Received encrypted confirmation.
  Permission denied.
  debug: Calling cleanup 0x414cf0(0x0)

sshd -d:
  debug1: sshd version OpenSSH_2.3.0p1
  debug1: Seeding random number generator
  debug1: read DSA private key done
  debug1: Seeding random number generator
  debug1: Bind to port 80 on 0.0.0.0.
  Server listening on 0.0.0.0 port 80.
  Generating 768 bit RSA key.
  debug1: Seeding random number generator
  debug1: Seeding random number generator
  RSA key generation complete.
  debug1: Server will not fork when running in debugging mode.
  Connection from 168.135.22.40 port 3635
  debug1: Client protocol version 1.5; client software version OpenSSH_2.3.0p1
  debug1: no match: OpenSSH_2.3.0p1
  debug1: Local version string SSH-1.99-OpenSSH_2.3.0p1
  debug1: Sent 768 bit public key and 1024 bit host key.
  debug1: Encryption type: 3des
  debug1: Received session key; encryption turned on.
  debug1: Installing crc compensation attack detector.
  debug1: Attempting authentication for illegal user k02189.
  Connection closed by 168.135.22.40
  debug1: Calling cleanup 0x4149e4(0x0)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-12-13 11:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 11:11 Rob_Hannah [this message]
2000-12-13 15:19 ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
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
2000-12-13 16:01 Rob_Hannah
2000-12-12 17:40 CyberZombie
2000-12-13  2:39 ` Corinna Vinschen
2000-12-13  5:31   ` CyberZombie
2000-12-13  5:52     ` Corinna Vinschen

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=OF17993F39.DEBF1922-ON862569B4.0068F021@deluxe.com \
    --to=rob_hannah@deluxe.com \
    --cc=cygwin@sourceware.cygnus.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).