Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 13 Jun 2001 15:13:19 +0200
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Inetd 1.3.2-14 problems
Message-ID:	<20010613151319.G1144@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<001301c0f389$4ab467a0$b66416ac AT spimageworks DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<001301c0f389$4ab467a0$b66416ac@spimageworks.com>; from dobrin@imageworks.com on Tue, Jun 12, 2001 at 02:47:35PM -0700

On Tue, Jun 12, 2001 at 02:47:35PM -0700, Bruce Dobrin wrote:
> Hi,
> 
> I just upgraded to cygwin 1.3.2 including the 1.3.2-14 inetutils.
> Everything except rshd works as well or better than it did before.  But now,
> when I try an interactive rsh to my cygwin1.3.2 machine, I can't for the
> life of me get beyond the passwd: prompt;  all I ever get is "Password
> Incorrect" regardless of what I type in....   I tried regenerating the
> passwd file (mkpasswd -d  and again with  mkpasswd -l)  and group files and
> ui-config files ,  I tried changing the passwd file  /bin/bash to /bin/sh
> (which fixed a similar problem on earlier releases).  I didn't have this
> problem with inetutils 1.3.2-11 since I went back to cygwin 1.3.1 (with the
> 1.3.2-11 inetutils) on one of my machines I no longer have this problem
> there.   But I'd like to solve this problem on 1.3.2-14   has anyone got any
> suggestions?

For some reason I can't reproduce that. BTW, it's not related to rshd
but to rlogind since rsh connects to rlogind when an interactive
sessions is started. In theory you should see the same effect when
using rlogin on the client side.

However, a typical reason for that problem is starting inetd under
an user account which may not switch user context.

Try the following. Try to login from another machine interactively
using rsh or rlogin but don't type in a password when it asks for
a password. Instead of, simply do nothing.
Then start a local interactive session on the server side and call
`ps -e'. You should see something like that:

$ ps -e
      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
     1648       1    1648       1648    ?   18 15:02:33 /usr/sbin/inetd
      892    1648    1648        892    ?   18 15:02:33 /usr/sbin/inetd
      816     892    1648       1572    ?   18 15:11:51 /usr/sbin/in.rlogind
     1112     816    1112       1608    2   18 15:11:51 /usr/bin/login
     1240       1    1240       1240  con  100 15:11:54 /usr/bin/tcsh
      136    1240     136       1636  con  100 15:11:55 /usr/bin/ps

Is the UID of inetd and the subsequent processes 18 as well for you
(which is the LocalSystem account)?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -