From owner-freebsd-security@FreeBSD.ORG  Wed Sep 24 07:44:27 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 5EA3816A4B3
	for <security@freebsd.org>; Wed, 24 Sep 2003 07:44:27 -0700 (PDT)
Received: from tenebras.com (laptop.tenebras.com [66.92.188.18])
	by mx1.FreeBSD.org (Postfix) with SMTP id AB0FC43FE1
	for <security@freebsd.org>; Wed, 24 Sep 2003 07:44:26 -0700 (PDT)
	(envelope-from kudzu@tenebras.com)
Received: (qmail 96892 invoked from network); 24 Sep 2003 14:44:26 -0000
Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241)
  by laptop.tenebras.com with SMTP; 24 Sep 2003 14:44:26 -0000
Message-ID: <3F71ADCA.7090408@tenebras.com>
Date: Wed, 24 Sep 2003 07:44:26 -0700
From: Michael Sierchio <kudzu@tenebras.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de
MIME-Version: 1.0
To: security@freebsd.org
References: <200309241429.h8OETrhk097904@freefall.freebsd.org>
In-Reply-To: <200309241429.h8OETrhk097904@freefall.freebsd.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:14.arp
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2003 14:44:27 -0000

FreeBSD Security Advisories wrote:

> IV.  Workaround
> 
> There is no known workaround at this time.

Using static ARP entries and turning off ARP on the interface
should be a workaround.  Whether this is remotely feasible
depends on your situation.