Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <39475830.C4D584CC@vinschen.de>
Date: Wed, 14 Jun 2000 12:02:24 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
Reply-To: cygwin <cygwin AT sourceware DOT cygnus DOT com>
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language: de, en
MIME-Version: 1.0
To: Stefan Norberg <stnor AT sweden DOT hp DOT com>
CC: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: openssh and inetd woes...
References: <JOEIICGFEHPPCFAMLANJGEMDCAAA DOT stnor AT sweden DOT hp DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stefan Norberg wrote:
> > Sorry but I can't reproduce that behaviour. I'm using sshd
> > as stand-alone service which runs with my own user account.
> 
> I nailed it down to bash. It works if I use "sh" as the shell. Why?

Because the path "/bin/sh" is hardcoded as the path to the default
shell, if ssh can't find another shell in the users /etc/passwd
entry. If you don't like it, you'll have to config _PATH_BSHELL
as another shell and moreover there are some hardcoded /bin/sh
calls in some sourcefiles which has to be changed by hand:

	session.c
	sshconnect.c

I've just mailed that problem to one of the OpenSSH maintainers.

> Corinna - are you researching the inetd Win32 stuff or is it in /dev/null?

I'm sorry again, I can't reproduce that on my system. I have
started sshd via inetd and the output of native win32 tools
is shown in my ssh xterm window as well as in ssh started from a
cmd window as expected. But I have seen a problem with xauth in
that configuration which I will (hopefully) get patched in my
next version of OpenSSH. Seems to be a permission problem.

Corinna

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com