From owner-freebsd-questions@FreeBSD.ORG Tue Aug 25 19:37:15 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0E7106568D for ; Tue, 25 Aug 2009 19:37:15 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-vw0-f189.google.com (mail-vw0-f189.google.com [209.85.212.189]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4748FC32 for ; Tue, 25 Aug 2009 19:37:15 +0000 (UTC) Received: by vws27 with SMTP id 27so3024702vws.3 for ; Tue, 25 Aug 2009 12:37:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=lqsWq4XHnZoJf7xuOafL+jhwHnF2M/5rYNLTud35yNE=; b=EzweiK7WGr8WKMY6wddQ19w5cCtRDfiLYvrqBmMJwdmfky29BPyfG3Fra7HK9BJEy1 GMPcurzjkMTK2RN8Ets6S1Pu9RfwG0Fcnag+YE8D/P88ZLwWd/yHXLNgmjIxTkZ/oEjH rSox0SaiTguHRQz+KiMsTReIUCWf9NhUD8B1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RCmKmk5FQRWU1w3vYznn+uPSTYhklvVaZ21CuVv5SP/ow4H0lvA9zdtNVQZ7rg4PUS Pd1iNfJoKotBd2otcQIWGZ/ACQvFrBSzbLG2QE4sI9OkbR5OnosAo497LUIVbo7Dq6oR lN4KrtrCgZj8nlff+/g2a9YFE7xaoZ5NeCsrY= MIME-Version: 1.0 Received: by 10.150.89.2 with SMTP id m2mr11270875ybb.73.1251229034477; Tue, 25 Aug 2009 12:37:14 -0700 (PDT) In-Reply-To: <20090825130616.20ab0049.wmoran@potentialtech.com> References: <4A924601.3000507@lim.nl> <25131646.post@talk.nabble.com> <200908251027.n7PARZBt009994@banyan.cs.ait.ac.th> <25132123.post@talk.nabble.com> <20090825082604.41cad357.wmoran@potentialtech.com> <25134277.post@talk.nabble.com> <20090825120504.93a7c51d.wmoran@potentialtech.com> <6201873e0908250921w46000c2by78893a1c5b581e78@mail.gmail.com> <20090825130616.20ab0049.wmoran@potentialtech.com> Date: Tue, 25 Aug 2009 14:37:14 -0500 Message-ID: <6201873e0908251237n5c819d9ag36f867b5e68e258c@mail.gmail.com> From: Adam Vande More To: Bill Moran Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Paul Schmehl , freebsd-questions@freebsd.org, Colin Brace Subject: Re: what www perl script is running? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:37:15 -0000 On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran wrote: > In response to Adam Vande More : > > > On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran >wrote: > > > > > In response to Paul Schmehl : > > > > > > > --On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace > > > wrote: > > > > > > > > > Bill Moran wrote: > > > > >> > > > > >> You can add an ipfw rule to prevent the script from calling home, > > > which > > > > >> will effectively render it neutered until you can track down and > > > actually > > > > >> _fix_ the problem. > > > > > > > > > > Mike Bristow above wrote: "The script is talking to 94.102.51.57 on > > > port > > > > > 7000". OK, so I how do I know what port the script is using for > > > outgoing > > > > > traffic on MY box? 7000 is the remote host port, right? > > > > > > > > > > FWIW, here are my core PF lines: > > > > > > > > > > pass out quick on $ext_if proto 41 > > > > > pass out quick on gif0 inet6 > > > > > pass in quick on gif0 inet6 proto icmp6 > > > > > block in log > > > > > > > > > > That is to say: nothing is allowed in unless explicitly allowed > > > > > Everything allowed out. > > > > > (plus some ipv6 stuff I was testing with a tunnel) > > > > > > > > > > > > > The problem with blocking outbound ports is that it breaks things in > odd > > > ways. > > > > For example, your mail server listens on port 25 (and possibly 465 as > > > well) but > > > > it communicates with connecting clients on whatever ethereal port the > > > client > > > > decided to use. If the port the client selects happens to be in a > range > > > that > > > > you are blocking, communication will be impossible and the client > will > > > report > > > > that your mail server is non-responsive. > > > > > > You're doing it wrong. Block on the destination port _only_ and you > don't > > > care about the ephemeral ports. > > > > What ports would you block then when you're trying to run a webserver? > > My point (which is presented in examples below) is that you block > everything > and only allow what is needed (usually only dns and ntp, possibly smtp if > the web server needs to send mail) > > That single statement above was directed specifically at the comment about > it being impossible to predict (and thus block) ephemeral source ports. > He's > right about that, and that's why filtering on the destination port is the > more common practice. > > Of course, that caused me to create an email that seems to contradict > itself, if you don't notice that it's two answers to two different > comments. My point was that it's unfeasible to block by destination point. You can only block by destination port if it's a known quantity, and the destination port is ephemeral in the question I posed(which what the OP had an issue with). > > > > > > It's much easier to block outgoing ports for services you *don't* > want to > > > > offer, but, if the service isn't running anyway, blocking the port is > > > > non-productive. > > > > > > You're obviously misunderstanding me completely. Your not blocking > > > incoming > > > connections, your preventing outgoing ones, which means there _is_ no > > > service running on your local machine. > > > > > > For example, a server that is _only_ web (with SSH for admin) could > have > > > a ruleset like: > > > > > > pass in quick on $ext_if proto tcp from any to me port {25,587,465,22} > keep > > > state > > > pass out quick on $ext_if proto tcp from me to any port {25} keep state > > > pass out quick on $ext_if proto upd from me to any port {53,123} keep > state > > > block all > > > > > > (note that's only an example, there may be some fine points I'm > missing) > > > > > > One thing that had not yet been mentioned when I posted my earlier > comment, > > > is that this system is a combination firewall/web server. That makes > the > > > rules more complicated, but the setup is still possible: > > > > > > pass in quick on $ext_if proto tcp from any to me port {80} keep state > > > pass out quick on $ext_if proto upd from me to any port {53,123} keep > state > > > pass out quick on $ext_if from $internal_network to any all keep state > > > block all > > > > > > Which allows limited outgoing traffic originating from the box itself, > > > but allows unlimited outgoing traffic from systems on > $internal_network. > > > > > > I've done this with great success. In fact, I had a fun time where a > > > client in question was infected with viruses out the wazoo, but the > > > viruses never spread off their local network because I only allowed > > > SMTP traffic to their SMTP relay, which required SMTP auth (thus the > > > viruses couldn't send mail) > > > > > > > > > > > > -- > > Adam Vande More > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > > -- > Bill Moran > http://www.potentialtech.com > http://people.collaborativefusion.com/~wmoran/ > -- Adam Vande More