From owner-freebsd-apache@FreeBSD.ORG Mon Mar 8 17:22:31 2010 Return-Path: Delivered-To: apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48D8D1065674 for ; Mon, 8 Mar 2010 17:22:31 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-px0-f195.google.com (mail-px0-f195.google.com [209.85.216.195]) by mx1.freebsd.org (Postfix) with ESMTP id 22B0D8FC13 for ; Mon, 8 Mar 2010 17:22:30 +0000 (UTC) Received: by pxi33 with SMTP id 33so2223910pxi.14 for ; Mon, 08 Mar 2010 09:22:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=+1LU6Zh+q0LcVpCGJsgvl3l2G95hfLlofhIiH+T5aow=; b=l9AcWJ1CfTUw6cbDneaddX8nUsma6Yv7VH9dgFMTrJA1u3o/HHPwEuNfeuEgomczRs d5mlCxqYn9BKLwKp/RYAkxPPh0p+0ZmFZ9l4+MxFGFGP8BjyN2S0oUFQHykIfr1EJczF +ZmNy6VQUBMxkPTvR3gKds2HVOsSe9yv/Kpsg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=yIR5gWhTkpsgAS+1pET0HX84ufzo9enFXDN+eSapdnYVG+jT7b4l4ih5plPbEdNvOp QCMatEceL7lfAcrNNCl0PZJy++ThJjIQvOVuaA/bed48xmQAG4RizT56qRU7/58rk0Lh ZQymzA9rlxbGO3vrzCpj1HcD+V3sc+PYO4pos= MIME-Version: 1.0 Received: by 10.143.21.13 with SMTP id y13mr3313911wfi.75.1268067374192; Mon, 08 Mar 2010 08:56:14 -0800 (PST) Date: Mon, 8 Mar 2010 11:56:14 -0500 Message-ID: <96af083b1003080856p620a2eaflf090507eee6caba5@mail.gmail.com> From: Adam Stylinski To: apache@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: apache22 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 17:22:31 -0000 Given this: http://tech.slashdot.org/story/10/03/08/1258200/Serious-Apache-Exploit-Discovered?from=twitter I suspect that the version in ports is affected by this vulnerability. Why is the latest version not 2.2.15 yet? Why is the auditdb not at least flagging apache22?