Message-ID: <000001c64d6a$104d95b0$0100000a@sphere>
From: "Glenn" <cygwin AT our DOT cable DOT nu>
To: <cygwin AT cygwin DOT com>
Subject: OpenSSH/SSHD Problem - seteuid 1005: Permission denied (WinXP 64-bit)
Date: Wed, 22 Mar 2006 15:35:07 +1100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com


I have a problem with "sshd" where it;
   (1) won't allow users to login, users recieve the message "Read from 
socket failed: Connection reset by peer"
   (2) "sshd" terminates prematurely.

The problem I believe (though I'm not really sure) relates to the second 
final line of output from the sshd server (see below)
   "seteuid 1005: Permission denied"
I'm running Windows XP 64-bit Edition -- it's my belief that seteuid cannot 
be called from a 32-bit context?? I could be wrong?? Though 
http://cygwin.com/faq/ seems to suggest that "Cygwin can be expected to run 
on all modern 32 bit versions [including] WOW64 32 bit environment on 
released 64 bit versions of Windows". In my config I've turned off privilege 
seperate ("UsePrivilegeSeparation no") -- however this didn't make any 
difference.

Does anyone know how I can fix this problem??! (see below for output from 
"/usr/sbin/sshd -D -d -e")

Regards,
   Glenn

****************************************
** Start sshd in debug mode to stdout:

[Glenn AT sphere] var [1:221] /usr/sbin/sshd -D -d -e
debug1: sshd version OpenSSH_4.3p2
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-D'
debug1: rexec_argv[2]='-d'
debug1: rexec_argv[3]='-e'
debug1: Bind to port 22222 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.

** Execute the command "ssh glenn AT 192 DOT 168 DOT 0 DOT 1" from another machine:

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: sshd version OpenSSH_4.3p2
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.0.40 port 1363
debug1: Client protocol version 2.0; client software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-1.99-OpenSSH_4.3
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user glenn service ssh-connection method none
debug1: attempt 0 failures 0
Failed none for glenn from 192.168.0.40 port 1363 ssh2
debug1: userauth-request for user glenn service ssh-connection method 
publickey
debug1: attempt 1 failures 1
debug1: test whether pkalg/pkblob are acceptable
debug1: temporarily_use_uid: 1005/513 (e=1002/513)
seteuid 1005: Permission denied
debug1: do_cleanup
[Glenn AT sphere] var [1:221]

** Sshd terminates prematurely
****************************************


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/