From owner-freebsd-questions@FreeBSD.ORG Wed Jul 8 13:55:55 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 1E222106564A for ; Wed, 8 Jul 2009 13:55:55 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id DE99A8FC19 for ; Wed, 8 Jul 2009 13:55:54 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 28048 invoked from network); 8 Jul 2009 13:55:54 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Jul 2009 13:55:54 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id BFC1A5081F; Wed, 8 Jul 2009 09:55:47 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 048131CCD5; Wed, 8 Jul 2009 09:55:46 -0400 (EDT) To: "chris\@darkadsl.ca" References: <40db8bb280d58ed7874492a66de0fa86@localhost> From: Lowell Gilbert Date: Wed, 08 Jul 2009 09:55:46 -0400 In-Reply-To: <40db8bb280d58ed7874492a66de0fa86@localhost> (chris@darkadsl.ca's message of "Tue\, 07 Jul 2009 15\:50\:06 -0700") Message-ID: <44bpnv2s9p.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Hacker problem...Takes down apache? 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: Wed, 08 Jul 2009 13:55:55 -0000 "chris@darkadsl.ca" writes: > I run a virtual hosting server and one of my clients got hacked (weak > password in CMS). Since you know the machine was hacked, you can't trust *anything* on the machine. If possible, you should rebuild it. If a jail was hacked, replacing that jail may be enough. You might be able to clean up the hack by reverse-engineering it, but you'll never be able to be sure you got everything. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/