From owner-freebsd-security Mon Jul 27 22:29:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04778 for freebsd-security-outgoing; Mon, 27 Jul 1998 22:29:49 -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 WAA04773 for ; Mon, 27 Jul 1998 22:29:47 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id BAA14633; Tue, 28 Jul 1998 01:29:04 -0400 (EDT) Date: Tue, 28 Jul 1998 01:29:04 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Jim Shankland cc: ben@rosengart.com, security@FreeBSD.ORG Subject: Re: inetd enhancements (fwd) In-Reply-To: <199807280440.VAA12658@biggusdiskus.flyingfox.com> 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, Jim Shankland wrote: > Careful there. The sockets API supports binding to a specific > *address*, not interface. If your machine has two interfaces > with addresses A and B, and you bind your server socket to address > B, it will happily accept connections addressed to address B, > but physically arriving via the "A" interface. Hrm, that's no good. But if I'm not mistaken, each interface is configured with its own address. Does this not give the system enough information to reject packets arriving on the wrong interface for their address? Are you sure that the system will accept packets for the wrong interface? 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