From owner-freebsd-security Tue Nov 17 05:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11416 for freebsd-security-outgoing; Tue, 17 Nov 1998 05:31:10 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from weathership.homeport.org (weathership.homeport.org [207.31.235.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11404 for ; Tue, 17 Nov 1998 05:31:05 -0800 (PST) (envelope-from adam@weathership.homeport.org) Received: (from adam@localhost) by weathership.homeport.org (8.8.8/8.8.5) id IAA17703; Tue, 17 Nov 1998 08:45:24 -0500 (EST) Message-ID: <19981117084523.A17686@weathership.homeport.org> Date: Tue, 17 Nov 1998 08:45:23 -0500 From: Adam Shostack To: Marc Slemko , Matthew Dillon Cc: freebsd-security@FreeBSD.ORG Subject: Re: Would this make FreeBSD more secure? References: <199811161941.LAA21747@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Marc Slemko on Mon, Nov 16, 1998 at 01:22:47PM -0800 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 16, 1998 at 01:22:47PM -0800, Marc Slemko wrote: | The other use, however, which is still very valid, is to secure the server | against untrusted users binding to the port. There are zillions of | protocols where the client can't verify the server in any useful way. | Requiring special privs. to bind to the port that the server runs as | helps this out in a big way. For this to be true, it requires that NT (which doesn't have a concept of privleged ports) to be removed from all server locations on the internet. While I'll agree that this is a useful security measure, its not particularly realistic, and we should consider giving up on this assumption. Adam -- "It is seldom that liberty of any kind is lost all at once." -Hume To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message