From owner-freebsd-security  Tue May  2 05:41:49 1995
Return-Path: security-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA03366
          for security-outgoing; Tue, 2 May 1995 05:41:49 -0700
Received: from redline.ru (root@mail.redline.ru [194.87.69.22])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA03339
          for <security@FreeBSD.org>; Tue, 2 May 1995 05:41:13 -0700
Date: Tue, 2 May 1995 16:38:55 +0400 (GMT+0400)
From: Anthony Graphics <agl@mac.glas.apc.org>
X-Sender: agl@mail.redline.ru
To: Brant Katkansky <bmk@dtr.com>
cc: security@FreeBSD.org
Subject: Re: Security options for NFS?
In-Reply-To: <199505021046.DAA00960@dtr.com>
Message-ID: <Pine.LNX.3.91.950502163618.21169A-100000@mail.redline.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: security-owner@FreeBSD.org
Precedence: bulk

On Tue, 2 May 1995, Brant Katkansky wrote:

> Date: Tue, 2 May 1995 03:46:49 -0700 (PDT)
> From: Brant Katkansky <bmk@dtr.com>
> To: security@FreeBSD.org
> Subject: Security options for NFS?
> 
> I'm looking to secure NFS and other services not covered by tcpd -
> what's the conventional wisdom for FreeBSD 2.0?
> 
> 
Try to compile NFSD 2.1 or 2.2alpha1 (do not remeber where it is:
check the back issues in comp.os.linux.announce) It does pretty the same
thing that tcpd does I believe although I don't know whether resulting
system would be considered "secure". A hint: never run pcnfsd ;-)
AGL