Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 8133

Summary: trouble getting rlogin to work with rsh-0.16-1.i386.rpm
Product: [Retired] Red Hat Raw Hide Reporter: dunwoody
Component: rshAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-01-05 21:16:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description dunwoody 2000-01-03 09:20:30 UTC
When I upgraded from rsh-0.10-28.i386.rpm to rsh-0.16-1.i386.rpm, rlogin
stopped working for me (rsh still works fine).

On the remote system, I get a normal-looking message in /var/log/messages:
    Jan  3 01:10:00 dunwoody1 in.rlogind[6248]: connect from
c130441-k.smateo1.sfba.home.com
    Jan  3 01:10:01 dunwoody1 pam_rhosts_auth[6248]: allowed to
dunwoody@c130441-k.smateo1.sfba.home.com as dunwoody

On the local system (running rlogin <remotesystem>), I simply get
a "connection closed" message.

Evidently rlogin got stricter in rsh-0.16-1 in a way that I don't
understand.  I've tried changing the permissions and contents of
my /etc/hosts, /etc/hosts.{allow,deny}, /etc/hosts.equiv, and
/etc/pam.d/rlogin in various ways, all to no avail -- I still
get "connection closed".
The documentation (e.g. man in.rlogind) doesn't seem to have changed
materially.  I'd greatly appreciate any suggestions.

Comment 1 Jeff Johnson 2000-01-05 21:16:59 UTC
Fixed in rsh-0.16-3 in Raw Hide. Make sure that you pick up the new
rsh-server-0.16-3 package, the fix is in /usr/sbin/in.rlogind in that
package.