Fwd: cygwin 1.7.1 cygrunsrv-sshd - unable to login

2010-01-15 Thread LogicDaemon
 Hi all.

I am trying to set up ssh server as service in standalone Windows 2003. Sorry 
if this already was questioned but I did not find anything related in near 
maillist archive.

After ssh-host-config I'm getting sshd service, which does not accept any 
logins (log -d -d attached, found nothing helpful there). However if I run 
/usr/sbin/sshd from cygwin shell, it starts and I am able to login with both 
certificate and keyboard-interactive methods. If I change ssh service login 
user to my login then I am able to login also. What may be wrong?

problem 2: first trials to set up service leaded to starting two cygrunsrv 
processes (parent and child) and one sshd. But now I am getting one cygrunsrv 
process and one sshd, and parent of sshd is not running. To stop process, I 
have to manually kill sshd. I already removed and reinstalled service and 
config file, but behavior persists.

--
 LogicDaemon

debug2: load_server_config: filename /etc/sshd_config
debug2: load_server_config: done config len = 212
debug2: parse_server_config: config /etc/sshd_config len 212
debug1: sshd version OpenSSH_5.3p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: rexec_argv[2]='-d'
debug1: rexec_argv[3]='-D'
debug2: fd 3 setting O_NONBLOCK
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: fd 4 clearing O_NONBLOCK
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.1.9 port 1264
debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60
debug1: no match: PuTTY_Release_0.60
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug2: fd 3 setting O_NONBLOCK
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: 
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: 
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit: 
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit: 
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: 
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: 
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: 
aes256-ctr,aes256-cbc,rijndael-...@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-ctr,aes128-cbc,blowfish-ctr,blowfish-cbc,3des-ctr,3des-cbc,arcfour256,arcfour128
debug2: kex_parse_kexinit: 
aes256-ctr,aes256-cbc,rijndael-...@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-ctr,aes128-cbc,blowfish-ctr,blowfish-cbc,3des-ctr,3des-cbc,arcfour256,arcfour128
debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5
debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5
debug2: kex_parse_kexinit: zlib,none
debug2: kex_parse_kexinit: zlib,none
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-sha1
debug1: kex: client-server aes256-ctr hmac-sha1 none
debug2: mac_setup: found hmac-sha1
debug1: kex: server-client aes256-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug2: dh_gen_key: priv key bits set: 254/512
debug2: bits set: 2035/4096
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug2: bits set: 2088/4096
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug2: cipher_init: set keylen (16 - 32)
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug2: cipher_init: set keylen (16 - 32)
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user logicdaemon service ssh-connection method none
debug1: attempt 0 failures 0
debug2: parse_server_config: config reprocess config len 212
Invalid 

Re: Fwd: cygwin 1.7.1 cygrunsrv-sshd - unable to login

2010-01-15 Thread Larry Hall (Cygwin)

On 01/15/2010 02:18 PM, LogicDaemon wrote:

  Hi all.

I am trying to set up ssh server as service in standalone Windows 2003.
Sorry if this already was questioned but I did not find anything related in
near maillist archive.

After ssh-host-config I'm getting sshd service, which does not accept
any  logins (log -d -d attached, found nothing helpful there). However if I 
run
/usr/sbin/sshd from cygwin shell, it starts and I am able to login with both
certificate and keyboard-interactive methods. If I change ssh service login
user to my login then I am able to login also. What may be wrong?

problem 2: first trials to set up service leaded to starting two
cygrunsrv  processes (parent and child) and one sshd. But now I am getting one
cygrunsrv process and one sshd, and parent of sshd is not running. To stop
process, I have to manually kill sshd. I already removed and reinstalled
service and config file, but behavior persists.


Forwarding multiple copies of the same message to this list will not gain you
any friends on this list.

I suggest you look at the email archives for issues with 'sshd' installations.
Most of them result from bad configuration, as is the case with yours (*never*
run 'sshd' directly from the command line as a user other than the one that
runs it as a service).

I also recommend two other things:

  1. Read the Users Guide for information about switching users.  I highly
 recommend you implement the LSA package option.
 http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview
  2. To quickly recover from the hole you're in, wipe your Cygwin installation
 and start over, using the configuration scripts (ssh-host-config, 
ssh-user-config)

 at your disposal and your new found knowledge from the Users Guide, email
 archives, and even the README.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
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