Bug 20590

Summary: rsh / rshd brocken
Product: Base System Reporter: Matthias Meyser <matthias>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-STABLE   
Hardware: Any   
OS: Any   

Description Matthias Meyser 2000-08-14 09:10:02 UTC
		Trying to configure rsh/rsh to do an
		"rsh machine ls" als root. 
		
		Configured ".rhosts". After getting some "permission denied"
		firgured out that I had to configure "pam.conf" altough.

		In "pam.conf" I just coppied all "login" lines and changed
                it to "rshd", commented out the original rshd entry.
		(why is ist disbaled by default ? )

		Now when I do an "rsh machine1 ls" from machine2 I get
		"assword:" as answer. At this Point I can enter enter any
		password I like even the right one but no will succed.
		Only way to exit is to press CTRL-C.

How-To-Repeat: 
		Just try to configure rsh
Comment 1 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-08-16 12:45:52 UTC
Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-16 14:42:58 UTC
State Changed
From-To: open->feedback

I can't reproduce the problem on the development branch of 
FreeBSD. 

Could you confirm that the following configuration exhibits 
the problem? 

> /etc/inetd.conf: 
shell   stream  tcp     nowait  root    /usr/libexec/rshd       rshd 

> /etc/hosts.allow: 
rshd: 127.0.0.1 : ALLOW 

> /etc/pam.conf: 
# all other rshd-related entries removed and replaced with... 
rshd    auth    required        pam_permit.so 

> /root/.rhosts: 
127.0.0.1 

> On the command-line: 
kill -HUP `cat /var/run/inetd.pid` 
rsh 127.0.0.1 ls 

This works fine here, and I'm pretty sure you've just got a mangled 
pam.conf.  I'll spare you the lecture about the insecurity of 
rsh when compared with ssh. ;-)
Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-16 16:00:49 UTC
State Changed
From-To: feedback->closed

Turns out that it was, in fact, the pam.conf configuration.