This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: openssh and inetd woes...
- To: Stefan Norberg <stnor at sweden dot hp dot com>
- Subject: Re: openssh and inetd woes...
- From: Corinna Vinschen <corinna at vinschen dot de>
- Date: Wed, 14 Jun 2000 12:02:24 +0200
- CC: cygwin <cygwin at sourceware dot cygnus dot com>
- References: <JOEIICGFEHPPCFAMLANJGEMDCAAA.stnor@sweden.hp.com>
- Reply-To: cygwin <cygwin at sourceware dot cygnus dot com>
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@sourceware.cygnus.com