From owner-freebsd-security Fri Nov 24 3:52:35 2000 Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8071837B479 for ; Fri, 24 Nov 2000 03:52:32 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA48969; Fri, 24 Nov 2000 12:52:15 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Nevermind Cc: Vlad , security@FreeBSD.ORG Subject: Re: ipf - icmp References: <20001124134218.A17181@nevermind.kiev.ua> From: Dag-Erling Smorgrav Date: 24 Nov 2000 12:52:14 +0100 In-Reply-To: Nevermind's message of "Fri, 24 Nov 2000 13:42:19 +0200" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nevermind writes: > > No. There is no way to completely prevent someone from tracerouting > > you. You can make it slightly harder by blocking incoming UDP (which > > your ruleset does not), but that's about it. > Why not to use ipfw? > ipfw add deny icmp from any to any via sis0 This still won't prevent traceroutes. The only 100% foolproof way to prevent anyone from tracerouting your machine is to take it off the net. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message