Bug 32750 - root rsh doesn't work (qa0322)
Summary: root rsh doesn't work (qa0322)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rsh
Version: 7.1
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-22 23:27 UTC by Joshua Buysse
Modified: 2007-03-27 03:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-22 23:27:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua Buysse 2001-03-22 23:27:19 UTC
rsh-server-0.17-2.5

The rsh protocol is not working as root.  The configuration has been
modified to allow root .rhosts using the magic -h parameter, as follows
(/etc/xinetd.d/rsh):

# default: on
# description: The rshd server is the server for the rcmd(3) routine and, \
#       consequently, for the rsh(1) program.  The server provides \
#       remote execution facilities with authentication based on \
#       privileged port numbers from trusted hosts.
service shell
{
        disable = no
        socket_type             = stream
        wait                    = no
        user                    = root
        log_on_success          += USERID
        log_on_failure          += USERID
        server                  = /usr/sbin/in.rshd
        server-args             = -h
}


Here's what appears in the logs:

Mar 22 17:23:10 scratchy pam_rhosts_auth[1281]: allowed to
root.umn.edu as root
Mar 22 17:23:10 scratchy in.rshd[1281]: rsh denied to
root.umn.edu as root: Permission denied. 
Mar 22 17:23:10 scratchy in.rshd[1281]: rsh command was 'pwd'

Comment 1 Joshua Buysse 2001-03-30 05:20:32 UTC
The pam_securetty module is causing the failure.  I'd request maybe a comment in
the man page or in the file /etc/xinetd.d/rsh to the effect that root rsh will
require an entry in /etc/securetty as 'rsh'.  Resolving as notabug.


Note You need to log in before you can comment on or make changes to this bug.