From owner-freebsd-questions Fri Jun 5 13:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00915 for freebsd-questions-outgoing; Fri, 5 Jun 1998 13:01:54 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00896 for ; Fri, 5 Jun 1998 13:01:33 -0700 (PDT) (envelope-from benh@blues.jpj.net) Received: from localhost (benh@localhost) by blues.jpj.net (backatcha) with SMTP id QAA10679; Fri, 5 Jun 1998 16:00:46 -0400 (EDT) Date: Fri, 5 Jun 1998 16:00:46 -0400 (EDT) From: Ben Hockenhull To: Jesse cc: freebsd-questions@FreeBSD.ORG Subject: Re: securing rsh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jesse, For starters, use ssh instead of rsh if at all possible. It is a drop in replacement for the r* utilities. Among the features are encrypted sessions and greater access control. ftp://ftp.cs.hut.fi/pub/ssh Ben -- Ben Hockenhull benh@jpj.net On Fri, 5 Jun 1998, Jesse wrote: > > Hi, > > It may be necessary on some of my systems to use rsh. I was wondering if > there were any guides or tips on securing the rhosts functions are much as > possible, such as with packet filtering, etc. > > Any pointers would be appreciated. Thanks! > > --- > Jesse > http://www.lumiere.net/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message