From hdm@demon.net  Tue Dec  2 04:26:37 1997
Received: from noc.demon.net (firewall-user@server.noc.demon.net [193.195.224.4])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA26488
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 2 Dec 1997 04:26:35 -0800 (PST)
          (envelope-from hdm@demon.net)
Received: by noc.demon.net; id MAA00516; Tue, 2 Dec 1997 12:26:30 GMT
Received: from stress.noc.demon.net(195.11.55.5) by inside.noc.demon.net via smap (3.2)
	id xma000511; Tue, 2 Dec 97 12:26:24 GMT
Received: from hdm by stress.noc.demon.net with local (Exim 1.73 #1)
	id 0xcrPC-0005TO-00; Tue, 2 Dec 1997 12:26:22 +0000
Message-Id: <E0xcrPC-0005TO-00.mailq@stress.noc.demon.net>
Date: Tue, 2 Dec 1997 12:26:22 +0000
From: hdm@demon.net
Reply-To: hdm@demon.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: rcmd(3) only allows one hardcoded connection method
X-Send-Pr-Version: 3.2

>Number:         5189
>Category:       bin
>Synopsis:       rcmd(3) only allows one hardcoded connection method
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec  2 04:30:01 PST 1997
>Closed-Date:    Tue Jun 15 13:47:57 PDT 1999
>Last-Modified:  Tue Jun 15 13:49:23 PDT 1999
>Originator:     Dom Mitchell
>Release:        FreeBSD 2.2.5-STABLE i386
>Organization:
Demon Internet Ltd.
>Environment:

Use of rsh and related protocols is being phased out in our network,
for security reasons.

>Description:

rmcd(3) uses the standard protocol of just opening a socket to the remote
host.  It should be able to use alternative, secure methods, such as
ssh.

>How-To-Repeat:

$ rdump -f remotehost:/dev/rmt0n /usr

The connection made will be an ordinary rsh-style one.

>Fix:

This problem has been fixed in OpenBSD since at least version 2.1.  They
have modified the standard library to use an "RSH" environment variable,
and call the command that it references.  The first step towards this
would be to get rcmd to call rsh instead of making the connection
directly.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: max 
Responsible-Changed-When: Tue Dec 2 06:25:54 PST 1997 
Responsible-Changed-Why:  
Misfiled PR. 
State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Wed May 27 02:47:57 PDT 1998 
State-Changed-Why:  
I am not convinced that this is a good idea, but lets see if somebody picks 
it up... 

From: Guy Helmer <ghelmer@cs.iastate.edu>
To: freebsd-gnats-submit@freebsd.org, hdm@demon.net
Cc:  
Subject: Re: bin/5189: rcmd(3) only allows one hardcoded connection method
Date: Thu, 03 Jun 1999 21:13:16 -0500

 No one has picked this up in over a year.  I agree with Poul (I'm not
 convinced it is a good idea), and this issue can usually be worked
 around, either by use of command line switches or by piping through
 ssh.  Can this be closed?
 
 Guy Helmer
 ghelmer@freebsd.org
 
State-Changed-From-To: suspended->closed 
State-Changed-By: ghelmer 
State-Changed-When: Tue Jun 15 13:47:57 PDT 1999 
State-Changed-Why:  
The original author could not be contacted, and consensus seems to be 
that this isn't a desired change. 
>Unformatted:
