From owner-freebsd-security Mon Jul 27 14:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15385 for freebsd-security-outgoing; Mon, 27 Jul 1998 14:38:42 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15286 for ; Mon, 27 Jul 1998 14:38:12 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA12680; Mon, 27 Jul 1998 17:37:35 -0400 (EDT) Date: Mon, 27 Jul 1998 17:37:32 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Robert Watson cc: freebsd-security@FreeBSD.ORG Subject: Re: inetd enhancements (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Jul 1998, Robert Watson wrote: > This seems like security to me -- the binding issue is especially relevant > to firewall hosts (multi-homed). Ever since I learned how the sockets API supports binding to a specific interface, I've wanted ways to use this in inet software. As it is, I'm using tcp_wrappers to get equivalent functionality, but this would certainly be more elegant. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message