Date: Mon, 31 Oct 2005 22:12:27 GMT From: matt wilbur <matt@photon.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/88301: unable to rsh to 5.4-STABLE system (10/14/05) with args Message-ID: <200510312212.j9VMCRMb084531@www.freebsd.org> Resent-Message-ID: <200510312220.j9VMKHk8051812@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 88301 >Category: misc >Synopsis: unable to rsh to 5.4-STABLE system (10/14/05) with args >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 31 22:20:16 GMT 2005 >Closed-Date: >Last-Modified: >Originator: matt wilbur >Release: 5.4-STABLE >Organization: PRA >Environment: FreeBSD wdc-mx.photon.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Oct 14 11:01:11 EDT 2005 jamie@wdc-mx.photon.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: Unable to rsh to host when proving a cmd to execute. rsh <5.4-stable host> works fine, gives a shell. rsh <5.4-stable host> ls gives this error: matt@photon ~ > rsh wdc-mx ls select: protocol failure in circuit setup. rsh: connection failed When I roll back to a 5.4-RELEASE rshd (which incidentally is not linked with libpam) it works fine. In both cases tcpdump shows the exact same exchange (given the exact same cmd given).. >How-To-Repeat: enable rshd in inetd.conf, verify /etc/pam.d/rsh is configured correctly, configure /etc/hosts.equiv or ~/.rhosts to allow rsh without password. rsh to "problem" system with a cmd to execute on distant end (eg rsh host ls). >Fix: roll back to 5.4-RELEASE rshd, works fine. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510312212.j9VMCRMb084531>