From owner-freebsd-security@FreeBSD.ORG Tue Mar 2 15:24:28 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36CA916A4CE for ; Tue, 2 Mar 2004 15:24:28 -0800 (PST) Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F2F443D1F for ; Tue, 2 Mar 2004 15:24:27 -0800 (PST) (envelope-from avalon@caligula.anu.edu.au) Received: from caligula.anu.edu.au (localhost [127.0.0.1]) by caligula.anu.edu.au (8.12.9/8.12.9) with ESMTP id i22NOQbF015448; Wed, 3 Mar 2004 10:24:26 +1100 (EST) Received: (from avalon@localhost) by caligula.anu.edu.au (8.12.9/8.12.8/Submit) id i22NOQ7B015446; Wed, 3 Mar 2004 10:24:26 +1100 (EST) From: Darren Reed Message-Id: <200403022324.i22NOQ7B015446@caligula.anu.edu.au> To: bms@spc.org (Bruce M Simpson) Date: Wed, 3 Mar 2004 10:24:25 +1100 (Australia/ACT) In-Reply-To: <20040302211030.GJ7115@saboteur.dek.spc.org> from "Bruce M Simpson" at Mar 02, 2004 09:10:30 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-security@freebsd.org Subject: Re: [PATCH] Force mountd(8) to a specified port. X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 23:24:28 -0000 In some mail from Bruce M Simpson, sie said: > Hi all, > > I have a requirement to run NFS read-only in an Internet-facing colocation > environment. I am not happy with packet filters alone around rpcbind, call > me paranoid, so I just spent the last few minutes cutting this patch. > > As you are aware, RPC applications can be forced to listen on a known port > through the sin/sa argument to bindresvport[_sa](). Why several Linux > distributions have this feature yet none of the BSDs do is beyond me... > > Please let me know your thoughts. If there are no valid objections I plan > to commit it. I'm confused by your first paragraph...the primary purpose of a patch like this would be, I imagine, to support being able to write filter rules for your firewall with a specific port defined rather than have to determine it after rpcbind & mountd have started. Darren