From owner-freebsd-security Fri Jun 9 8:22:40 2000 Delivered-To: freebsd-security@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 63ADE37C402 for ; Fri, 9 Jun 2000 08:22:36 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 130Qc4-0007DI-00 for freebsd-security@freebsd.org; Fri, 09 Jun 2000 11:22:24 -0400 Date: Fri, 9 Jun 2000 11:22:24 -0400 From: Peter Radcliffe To: freebsd-security@freebsd.org Subject: Re: Firewall Problem Message-ID: <20000609112223.A27490@pir.net> Reply-To: freebsd-security@freebsd.org Mail-Followup-To: freebsd-security@freebsd.org References: <862568F9.003E54A8.00@MCSMTP.MC.VANDERBILT.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jus@security.za.net on Fri, Jun 09, 2000 at 01:34:22PM +0200 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin Stanford probably said: > You can kill the portmapper (port 111) in /etc/rc.conf by placing an > override in there (find the override in /etc/defaults/rc.conf). > > Port 6000 is your X server - its best to firewall out 6000. In this day and age I _strongly_ suggest starting X with '-nolisten tcp' and using the unix domain socket to talk to the X server. This even works cleanly with X forwarding over ssh. This will stop X clients on another machine displaying on your's (unless you use ssh forwarding) but I never do that anyway ... P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message