On 23.08.2012 13:29, Jeff Trawick wrote:
On Thu, Aug 23, 2012 at 4:41 AM, Rainer Jung <[email protected]> wrote:
On 23.08.2012 09:57, Plüm, Rüdiger, Vodafone Group wrote:
-----Original Message-----
From: Plüm, Rüdiger, Vodafone Group
Sent: Donnerstag, 23. August 2012 09:55
To: [email protected]
Subject: RE: [Vote] httpd 2.2.23 release
-----Original Message-----
From: Jeff Trawick [mailto:[email protected]]
Sent: Donnerstag, 23. August 2012 03:17
To: [email protected]
Subject: Re: [Vote] httpd 2.2.23 release
On Tue, Aug 21, 2012 at 3:25 PM, William A. Rowe Jr.
<[email protected]> wrote:
Candidate binaries are available from
http://httpd.apache.org/dev/dist/ -
these do not yet constitute ASF releases. Win32 specific artifacts
(x86 binary distribution and -win32-src.zip) will follow sometime
later
this evening.
Feedback and edits to the draft announcement are greatly
appreciated,
since we need to better position 2.2 as 'just maintenance' and we
can
drop some of the 'shiny new' bits of that Announcement text, given
that
it is old hat now, and they should be reading the 2.4 Announce
(which
this document now links to).
So, for your consideration, a vote...
[+1] Release httpd 2.2.23 as GA
I get this testing both 2.2.22 and 2.2.23 on Linux 64-bit:
# Failed test 2 in t/security/CVE-2008-2364.t at line 19
# Failed test 3 in t/security/CVE-2008-2364.t at line 22
Hm. Which Linux? I have never seen these on Centos 64 Bit.
Perl used on Centos (5):
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
It should be this
https://github.com/gisle/libwww-perl/commit/25f86ba92ebf3d0abcf45cfda1880a1a12a91a0b
change in LWP. Changed on April 11, 2011, so probably only part of the
latest LWP 6.0.3.
Jeff: can you confirm the your libwwww is indeed this latest version 6.0.3?
$ perl -MLWP -le "print(LWP->VERSION)"
6.04
OK, even newer. Wasn't in the tag list for LWP in their git, so I
thought 6.0.3 was latest. But the suspect code is also in 6.0.4. So I'd
say the test failure is a result of the above change in Perl LWP. No
idea though, how the test framework could work around this.
Regards,
Rainer
