X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:  Re: ssh to 2003 server exist immediately
Date:  Sat, 13 May 2006 20:27:59 -0700
Lines: 63
Message-ID: <e46840$87e$1@sea.gmane.org>
References:  <e3s32l$k60$1 AT sea DOT gmane DOT org> <4461FD21 DOT 3050606 AT cygwin DOT com> <e3t060$q2n$1 AT sea DOT gmane DOT org> <44622D6F DOT 2090303 AT cygwin DOT com> <e3u80a$vbr$1 AT sea DOT gmane DOT org> <e3ubdt$cdt$1 AT sea DOT gmane DOT org> <446542EF DOT 8080204 AT cygwin DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
In-Reply-To: <446542EF.8080204@cygwin.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Larry Hall (Cygwin) wrote:
> Andrew DeFaria wrote:
>> Andrew DeFaria wrote:
>>> /etc/passwd and /etc/group are symlinks to a shared and up to date 
>>> copy of the output of mkpasswd/mkgroup. That's not the issue. As I 
>>> understand it, for sshd (or in.rlogind) to "switch user" it needs 
>>> special privileges. Indeed the documentation alludes to that. And 
>>> until I added those permissions to the sshd_server user ssh/rsh 
>>> would not work at all. (rsh, started from inetd that is as inetd was 
>>> also logging on as the sshd_server user). Still, while rsh works, 
>>> ssh refuses to work citing the error message above in 
>>> /var/log/sshd.log. IOW I can rsh <server> and get in. I can also rsh 
>>> <server> <command> and have <command> run on <server> (provided 
>>> /etc/passwd on <server> has a blank password for the user). However 
>>> I cannot ssh <server>. When I do so it prompts for the password then 
>>> abruptly logs out with the only clue left in 
>>> <server>:/var/log/sshd.log.
>> A little more info. rsh <server> works. rsh <server> <command> hangs!
>>
>> sons-clearcase:rsh sons-sc-cc
>> No directory /us/adefaria!
>> Logging in with home = "/".
>> Last login: Wed May 10 20:31:46 from sons-clearcase.salira.com
>> CYGWIN_NT-5.2 SONS-SC-CC 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
>> WARNING: HOME directory did not exist! Logging in with HOME = /tmp
>>
>> adefaria AT SONS-SC-CC ~
>> $ logout
>> rlogin: connection closed.
>> sons-clearcase:rsh sons-sc-cc id
>>
>> This is very frustrating because my client relies on a command I 
>> wrote called "smake" which essentially boils down to: "rsh <server> 
>> -n cd <directory> && make" that is intended to perform the make on 
>> <server>. As you can see it relies on rsh, passwordless login to 
>> <server> executing a command. But with this new 2003 server rsh 
>> <server> <command> hangs!
>>
>> Help!
> Are you sure you're not getting caught by the Windows rsh?
Positive:

$ which rsh
/bin/rsh
$ rsh --help
Usage: rsh [-nd] [-l USER] [USER@]HOST [COMMAND [ARG...]]
Execute COMMAND on remote system HOST

  -d, --debug                Turn on socket debugging
  -l USER, --user=USER       Run as USER on the remote system
  -n, --no-input             Use /dev/null as input
      --help                 Give this help list
  -V, --version              Print program version

Submit bug reports to <bug-inetutils AT gnu DOT ai DOT mit DOT edu>.
$ rsh sons-sc-cc id
<hangs>

I have seen in.rshd.exe.stackdump's but I forget where... Could this 
likewise be caused by that failure to load ws2_32.dll?
-- 
If bankers can count, how come they have eight windows and only four 
tellers?


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