From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PbfwF-0006H6-2O for garchives@archives.gentoo.org; Sat, 08 Jan 2011 21:03:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E36BAE0531 for ; Sat, 8 Jan 2011 21:03:01 +0000 (UTC) Received: from mail2.viabit.com (mail2.viabit.com [65.246.80.16]) by pigeon.gentoo.org (Postfix) with ESMTP id 915B8E0262 for ; Sat, 8 Jan 2011 20:21:12 +0000 (UTC) Received: from [172.17.29.6] (unknown [65.213.236.242]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail2.viabit.com (Postfix) with ESMTPSA id EDAFE37AFD for ; Sat, 8 Jan 2011 15:21:11 -0500 (EST) Message-ID: <4D28C733.2020907@orlitzky.com> Date: Sat, 08 Jan 2011 15:21:07 -0500 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101221 Lightning/1.0b3pre Thunderbird/3.1.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-hardened@lists.gentoo.org Reply-to: gentoo-hardened@lists.gentoo.org MIME-Version: 1.0 To: gentoo-hardened@lists.gentoo.org Subject: Re: [gentoo-hardened] UDEREF vs. Apache MMAP References: <4D27EEA5.6080301@orlitzky.com> <4D28621E.27194.73F0E0A0@pageexec.freemail.hu> <4D28AB4D.3020609@gentoo.org> In-Reply-To: <4D28AB4D.3020609@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 0510cf45-d961-4967-8ecf-f988aa808eda X-Archives-Hash: 8b141956fb20e14ebbf63efb50a634dc On 01/08/2011 01:22 PM, Anthony G. Basile wrote: > On 01/08/2011 07:09 AM, pageexec@freemail.hu wrote: >> On 7 Jan 2011 at 23:57, Michael Orlitzky wrote: >> >>> I was able to figure out my new apache problem. It seems that >>> PAX_MEMORY_UDEREF and apache's EnableMMAP directive don't get along >>> sometimes: >> >> this one should have already been fixed in one of this week's patches, >> but i'm not sure if it's in any hardened release yet. you could try the >> latest grsec patch directly and see if it actually resolves the issue. >> > > Okay Michael, can you try: > > hardened-sources-2.6.32-r33 > > and/or > > hardened-sources-2.6.36-r8 > > Both are based on the latest grsecurity-*-201101052002.patch Back to normal with hardened-sources-2.6.36-r8. Thanks again guys.