From owner-freebsd-security Sun Jul 22 17: 7:33 2001 Delivered-To: freebsd-security@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id 0D0D237B406 for ; Sun, 22 Jul 2001 17:07:29 -0700 (PDT) (envelope-from durham@w2xo.pgh.pa.us) Received: from jimslaptop.int (jimslaptop.int [192.168.5.8]) by w2xo.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f6N0F7m29933; Sun, 22 Jul 2001 20:15:08 -0400 (EDT) (envelope-from durham@w2xo.pgh.pa.us) Date: Sun, 22 Jul 2001 20:07:38 -0400 (EDT) From: Jim Durham X-X-Sender: To: serkoon Cc: Subject: Re: rpc.statd attacks In-Reply-To: <002e01c1129c$5b0ef6b0$0200000a@kilmarnock> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 22 Jul 2001, serkoon wrote: > > However, since I have port 111 blocked in the firewall, > > how in the world is even an error message being generated? > > I have even portscanned and 111 is not open to the outside. > > Firewall UDP:111 or kill portmapd (if you don't need it). > I'm using NFS internally, so I need portmapd and 111 udp is blocked. That's what is bothering me.. -Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message