pdate (now on github) and CVE
> announcement (if any) now that part of the process is handled elsewhere).
>
+1
To my knowledge, the publishing of the site and overhaul of the new CVE
process are the things requiring updates.
--
Daniel Ruggeri
> The CVE announcement should be much
e candidate for processing it
with announce.sh, so I'm happy to encode whatever we consider the best
way forward into that script.
--
Daniel Ruggeri
On 8/7/2020 8:56 AM, William A Rowe Jr wrote:
> Following the announcement link, it isn't clear that
>
> https://httpd.apache.o
it's just because the text was
bumped as-is from the 'dev' location to the 'dist' location.
--
Daniel Ruggeri
On August 5, 2020 7:23:33 AM CDT, Rainer Jung wrote:
>Could you fix the date (September 21, 2018 sems wrong).
>
>Thanks!
>
>Rainer
>
>Am 0
t way to wrap up the week!
Here are the votes I recorded during the thread:
PMC
jailletc36, steffenal, elukey, jorton, jfclere, ylavic, covener,
gbechis, gsmith, druggeri, jblond, rjung
Community
Noel Butler, wrowe
--
Daniel Ruggeri
On 8/1/2020 9:13 AM, Daniel Ruggeri wrote:
> Hi, all;
>
apr-util: "1.6.1"
iconv: "1.2.2"
brotli: "1.0.7"
nghttp2: "1.41.0"
zlib: "1.2.11"
pcre: "8.44"
libxml2: "2.9.9"
php: "7.4.8"
lua: "5.3.5"
curl: "7.71.1"
--
Sure - I'll commit the following:
*) mod_proxy_fcgi: Fix missing APLOGNO macro argument
Straight forward enough. Thanks for the correction.
--
Daniel Ruggeri
On 8/1/2020 9:14 AM, Steffen wrote:
> Not agree. Fixes APLOGNO it for all platforms. Only I reported warnings on
> Window
c2
*httpd-2.4.46.tar.gz
sha512:
5801c1dd0365f706a5e2365e58599b5adac674f3c66b0f39249909841e6cdf16bfdfe001fbd668f323bf7b6d14b116b5e7af49867d456336fad5e685ba020b15
*httpd-2.4.46.tar.gz
The SVN tag is '2.4.46' at r1880505.
--
Daniel Ruggeri
Agreed - thank you (everyone) for the quick rally to fix this and for
confirming we don't have other work needing to be done. I apologize for
taking almost 24 hours to ACK and get us moving again.
I've updated CHANGES and will send a VOTE shortly
--
Daniel Ruggeri
On 7/31/2020 1:28
2.4.46 when we are all buttoned up with the warnings.
--
Daniel Ruggeri
On 7/29/2020 10:26 AM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the n
> Agreed. And Steffen points out there is precedence.
>
Aye - and I'd hate to appear inconsistent :-)
Version numbers are cheap - I'll re-roll when we have confirmation all
is good in the 2.4 branch.
--
Daniel Ruggeri
: "1.1.1g"
openldap: "2.4.50"
apr: "1.7.0"
apr-util: "1.6.1"
iconv: "1.2.2"
brotli: "1.0.7"
nghttp2: "1.41.0"
zlib: "1.2.11"
pcre: "8.44"
libxml2: "2.9.9"
php: &q
ae
*httpd-2.4.45.tar.gz
sha512:
8b1e9c22371c75efd2466c69ed48782ddcecfe0a3ff143ca3f9cb720ea2aee56f5c323a9e3ae80cd5c44f1601b5894879af03b6b3729a8ca0555bb5193a1296a
*httpd-2.4.45.tar.gz
The SVN tag is '2.4.45' at r1880411.
--
Daniel Ruggeri
On 7/28/2020 12:51 PM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this
> candidate tarball as 2.4.44:
Hi, Stefan;
Since version numbers are cheap and we've had only one vote on this
one, I don't see harm in incorporating the change and rerolling. Doubly
so since votes are already in for the change and all that. I'll re-roll
the release tarball once you confirm.
--
Daniel Rugger
: x86_64
libraries:
openssl: "1.1.1g"
openldap: "2.4.50"
apr: "1.7.0"
apr-util: "1.6.1"
iconv: "1.2.2"
brotli: "1.0.7"
nghttp2: "1.41.0"
zlib: "1.2.11"
pcre: "8.44"
libxml2:
9e
*httpd-2.4.44.tar.gz
sha512:
f9065b30df4d91b70739631e19e65c5a68d4f4ed9071c2b040176b5ee839a86078f178cadd8430f325edda8dddf1ff95c7924e62d73f8f3b6e9b7f48f0b3b257
*httpd-2.4.44.tar.gz
The SVN tag is '2.4.44' at r1880378.
--
Daniel Ruggeri
On 7/28/2020 7:41 AM, Eric Covener wrote:
> On Tue, Jul 28, 2020 at 4:30 AM Christophe JAILLET
> wrote:
>> Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
>>>
>>> On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
>>> wrote:
>>>>
On July 27, 2020 2:12:45 AM CDT, Stefan Eissing
wrote:
>
>
>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri :
>>
>> Hi, all;
>> FYI, I came across an unexpected set of diffs when rebuilding docs
>before tagging this morning. Haven't forgotten about
eeing.
On 2020/07/22 23:32:05, Daniel Ruggeri wrote:
> Hi, all;
>It's been a while since we've rolled a release and gotten fixes/etc in our
> community's hands. Apologies for not suggesting this sooner. How about a T&R
> Friday? That will let vote run through the weekend.
> --
> Daniel Ruggeri
re, we need three
committer +1s to backport. Once all three are in place, the proposer (or
release manager) commits the change to the branch. So, for this one, I
think we're not quite ready to incorporate.
P.S.
I hope all is well - long time no chat!
--
Daniel Ruggeri
On 7/23/2020 1:33 PM, Chr
Hi, all;
It's been a while since we've rolled a release and gotten fixes/etc in our
community's hands. Apologies for not suggesting this sooner. How about a T&R
Friday? That will let vote run through the weekend.
--
Daniel Ruggeri
we are discussing ideas in this neighborhood, one thing to keep in
mind is that during release of security fixes, sometimes there are items
added to CHANGES and sometimes CHANGES is modified to add CVE
information. There have been minor bumps in the road where these patches
don't always apply cleanly. So, if possible, it would be great to
consider. There may be nothing to do, though, since that happens way
after backport.
--
Daniel Ruggeri
ppens, I can look into it
further.
If it's too complicated a fix, I'm OK with removing that line from
the description. The CVE reports must include the version vulnerability
info in the description, but it's not really a requirement for the site
(I was just keeping them consistent).
--
Daniel Ruggeri
On 3/26/2020 9:50 AM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this
> candidate tarball as 2.4.43:
>
hanks, Bill. Shall this response be considered a +1 for the purposes of
the release vote?
--
Daniel Ruggeri
On 3/26/2020 9:50 AM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this
> candidate tarball as 2.4.43:
>
7f
*httpd-2.4.43.tar.gz
sha512:
d9879b8f8ef7d94dee1024e9c25b56d963a3b072520878a88a044629ad577c109a5456791b39016bf4f6672c04bf4a0e5cfd32381211e9acdc81d4a50b359e5e
*httpd-2.4.43.tar.gz
The SVN tag is '2.4.43' at r1875715.
--
Daniel Ruggeri
Hi, all;
Per the issues surfaced/fixed, I'll go ahead and declare this release
as dead-on-the vine. I'll target another T&R later this week, hopefully
after the discussion around OpenSSL versioning plays out.
How about Thursday?
--
Daniel Ruggeri
On 3/19/2020 9:45 AM,
d
*httpd-2.4.42.tar.gz
sha512:
09d0f3bd9266907eea91ac9129a3c41658929b9fd88d627c1fccceaf952548d2c3ad62099b9bcd1ae4822402c1dbda90b8bfb9f64cd5eac9f84ed249faffb837 *httpd-2.4.42.tar.gz
The SVN tag is '2.4.42' at r1875427.
--
Daniel Ruggeri
Hi, all;
It looks like we're in a good place to do a release so I will aim to
T&R 2.4.42 tomorrow. Please feel free to shout loudly if any issues are
found.
--
Daniel Ruggeri
Sure - happy to oblige!
--
Daniel Ruggeri
On 2020-03-13 07:51, Eric Covener wrote:
Looks like STATUS is in good shape.
Any cycles Daniel or Jim?
--
Eric Covener
cove...@gmail.com
On February 7, 2020 4:59:39 AM CST, Joe Orton wrote:
>On Thu, Feb 06, 2020 at 07:52:18AM -0600, Daniel Ruggeri wrote:
>> Hey there, Joe; No idea how I didn't detect this much sooner. I have
>>access to hardware security modules with PKCS11 interfaces for key
>
>
Hi, all. It's been a few months since we've rolled a release and there are a
few bug fixes that seem like A Good Thing to get out there.
Thoughts on rolling soon-ish?
As always, I volunteer to either RM or mentor someone new through the RM
process.
--
Daniel Ruggeri
sl_pkcs11.patch
> + +1: jorton,
> +
> PATCHES/ISSUES THAT ARE BEING WORKED
>[ New entries should be added at the START of the list ]
>
>
>
>
--
Daniel Ruggeri
On 8/9/2019 8:50 AM, sebb wrote:
> On Fri, 9 Aug 2019 at 14:40, Daniel Ruggeri wrote:
>> Hi, all;
>> Please find below the proposed release tarball and signatures:
>> https://dist.apache.org/repos/dist/dev/httpd/
>>
>> I would like to call a VOTE over the next f
27;
>> +$ENV{STATUS_UPDATE} =~ s/^\s*$//g;
>> +die "Status update not found!" if !$ENV{STATUS_UPDATE};
>> +open(CHANGES, "$ENV{UPDATE_FILE}"); my @content=;
>> close(CHANGES);
>> +foreach my $line (@content) {
>&
Ah, yes... Not sure how I made that error. Just fixed!
--
Daniel Ruggeri
On August 17, 2019 9:41:42 AM CDT, Stefan Fritsch wrote:
>Hi,
>
>Shouldn't CVE-2019-10097 be listed under 2.4.41, too?
>
>Cheers,
>Stefan
>
>--- httpd/httpd/branches/2.4.x/CHANGES 2019/08/14 20
tions
and will prep for announcement in 48-ish hours.
--
Daniel Ruggeri
On 2019/08/09 13:40:38, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this candidate
> tarball as 2.4.
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: b713e835aa7cde823a4b7f8e3463164f3d9fe63e *httpd-2.4.41.tar.gz
sha256: 3c0f9663240beb0f008acf3b4501c4f339d7467ee345a36c86c46b4d6f3a5461
*httpd-2.4.41.tar.gz
--
Daniel Ruggeri
Yessir. I'll send a notification when ready.
--
Daniel Ruggeri
On August 8, 2019 11:54:18 AM CDT, Dennis Clarke wrote:
>On 8/8/19 7:41 AM, Daniel Ruggeri wrote:
>> Hi, all;
>> As the subject says, I'd like to get on with our 2.4.new release now
>> that we're
+1
--
Daniel Ruggeri
On August 8, 2019 8:09:57 AM CDT, Eric Covener wrote:
>CC dev@ I assumed this was safe to just assert.
>
>On Thu, Aug 8, 2019 at 9:08 AM wrote:
>>
>> Author: covener
>> Date: Thu Aug 8 13:08:33 2019
>> New Revision: 1864701
>>
&
Hi, all;
As the subject says, I'd like to get on with our 2.4.new release now that
we're good to go. Will kick things off in about 24 hours
--
Daniel Ruggeri
we'll be
back again soon!
--
Daniel Ruggeri
On August 3, 2019 8:51:07 AM CDT, Daniel Ruggeri wrote:
>Hi, all;
> Please find below the proposed release tarball and signatures:
>https://dist.apache.org/repos/dist/dev/httpd/
>
>I would like to call a VOTE over the next few da
Thanks, Jan;
I'm afraid I have no way to verify or dig into Windows-specific issues. Can
you share more information or errors that can help, or is this related to the
things already discussed on the list?
--
Daniel Ruggeri
On August 4, 2019 6:33:58 AM CDT, Jan Ehrhardt wrote:
>Gre
the internal
client error to be treated as a "pass" of a test it cannot run.
--
Daniel Ruggeri
>
> Regards,
>
> Rainer
>
> Am 02.04.2019 um 12:44 schrieb jor...@apache.org:
>> Author: jorton
>> Date: Tue Apr 2 10:44:12 2019
>> New Revision: 185680
a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: 31bc6f87ac209010b8b364abc1c80dfaee53cc64 *httpd-2.4.40.tar.gz
sha256: 451e6cf6caa09119900b74652266427f70050de5c51948acd4aaaf60d0d3cad0
*httpd-2.4.40.tar.gz
--
Daniel Ruggeri
Ahhh! I did send a VOTE email, but it looks like it never made it
through to the list!
I will retry from my ASF address through the ASF mail relay...
Date: Fri, 02 Aug 2019 15:18:57 -0500
From: Daniel Ruggeri
To: dev@httpd.apache.org
Subject: [VOTE] Release httpd-2.4.40
Message-ID:
X-Sender
Hrm... I see this never made it to the list! Retrying from my apache.org
address...
--
Daniel Ruggeri
Director, VP Fundraising, member, httpd PMC
The Apache Software Foundation
On July 31, 2019 8:18:41 AM CDT, Daniel Ruggeri wrote:
>Hi, all
>I see we have a number of backports ready to
2019-05-11
Key fingerprint = E348 0043 5956 21FE 5610 5F11 2AB1 2A7A DC55 C003
uid Daniel Ruggeri (http://home.apache.org/~druggeri/)
uid Daniel Ruggeri
uid [jpeg image of size 13027]
sub 4096R/14FF4720 2019-05-11
It would be
Karaf
Drill
Observability
Beam
*maybe* that has has an effect on folks' submissions? Dunno... I just submitted
in "general"
--
Daniel Ruggeri
On 2019/05/01 20:35:49, Rich Bowen wrote:
> Hi, folks.
>
> The call for presentations for ApacheCon North America closes in a
I just don't think I have enough time to develop expertise in
mod_md or H2) so keep the suggestions coming.
What about a "stupid httpd tricks" kind of talk which is an amalgamation of
neat stuff? I'm sure we could come up with at least two dozen examples EASILY.
--
Daniel Rugg
The announcement message was also rejected by moderators because we don't have
KEYS directly linked on the download page.
I will correct both (about three hrs from now) and reattempt announcement.
--
Daniel Ruggeri
On April 2, 2019 1:01:31 AM CDT, Marion et Christophe JAILLET
wrote
itself!
I shall forthwith begin the distribution of the release tarball to the
mirrors.
--
Daniel Ruggeri
On 3/27/2019 10:09 AM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
>
On 3/27/2019 10:09 AM, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this
> candidate tarball as 2.4.39:
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: e66d6bfea42254e64d3b5009f49ecc486ac46de2 *httpd-2.4.39.tar.gz
sha256: 8b95fe249f3a6c50aad3ca125eef3e02d619116cde242e1bc3c266b7b5c37c30
*httpd-2.4.39.tar.gz
--
Daniel Ruggeri
On 2019/03/23 13:43:20, Daniel Ruggeri wrote:
> Hi, all;
>
> I see there are several things ready for release in 2.4.x so I'd like
> to go ahead and get those things into our community's hands by rolling
> in the next few days.
>
> Please do shout lo
h to do the T&R
--
Daniel Ruggeri
Updated in r1854645 and published to the site. I made a slight
modification to the line I suggested yesterday to note that TLS 1.3 also
requires openssl-1.1.1, too.
I've also purged the old release from dist in r32727.
Thanks for the pointers. Have a great weekend!
--
Daniel Ruggeri
O
e it is an important feature.
I will update the landing page and remove .37 from dist later today or
tomorrow morning at the latest (unless someone beats me to it).
--
Daniel Ruggeri
On February 28, 2019 1:05:40 PM CST, William A Rowe Jr
wrote:
>I was just updating PR 63212 and could not poin
On February 22, 2019 5:03:43 AM CST, Ruediger Pluem wrote:
>
>
>On 02/21/2019 12:46 AM, Daniel Ruggeri wrote:
>> Hi, all;
>> I was approached to see if I would be interested/willing to work on
>code to support encrypted client keys for the proxy.
>
>You mean
I know it's an odd thing to ask, but thought it's worth bringing up because
I'd personally love to see this functionality :-)
Feel free to reply directly to me if you don't want to share with the list.
--
Daniel Ruggeri
On 2019-01-22 11:39, Daniel Gruno wrote:
On 1/22/19 6:08 PM, Daniel Ruggeri wrote:
Hi, Cristophe;
Thanks for the extra eye. Fortunately, this is expected behavior.
Since the announcement goes out on some future date, the date is fixed
up later in the announce.sh script.
Daniel, could
Hi, Cristophe;
Thanks for the extra eye. Fortunately, this is expected behavior.
Since the announcement goes out on some future date, the date is fixed
up later in the announce.sh script.
--
Daniel Ruggeri
On 2019-01-21 13:22, Marion & Christophe JAILLET wrote:
Fixed in r32079.
I ho
Community
Noel Butler, Dennis Clark
I thank everyone for their time in testing and verifying this latest
release. I will begin the process of promoting to the mirrors for sync.
--
Daniel Ruggeri
On 1/20/2019 4:25 PM, Noel Butler wrote:
>
>
>>
>> It's not just good, it's good enough!
>>
>
> tongue in cheek here, but...
> shouldn't that be the other way around, "It's not just good enough,
> it's good!" :)
>
haha - tounge in cheek indeed. The line, "It's not just good, it's good
e
On 2019-01-17 12:49, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.38:
[ ] +1: It's not just good,
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: 6ee19a7b936a6ddbbf81b313c4a8b38bf232b40e *httpd-2.4.38.tar.gz
sha256: 38d0b73aa313c28065bf58faf64cec12bf7c7d5196146107df2ad07541aa26a6
*httpd-2.4.38.tar.gz
--
Daniel Ruggeri
Thank you, folks. I apologize again for the embarrassing mistake.
Will be sending along the updated vote email in a few seconds.
--
Daniel Ruggeri
On 2019-01-17 12:30, Yann Ylavic wrote:
We should at the same 2.4.x state as before the release try now, I
think the script(s) can be restarted
;ll redo in about 30 more minutes - with the right version number fed
to the machine.
--
Daniel Ruggeri
On 2019-01-17 11:51, William A Rowe Jr wrote:
One problem with scripts, they do just what they are told.
You just tagged 2.4.39 as 2.4.38.
Please revert to 2.4.38 and tag - until the tarballs
On 2019-01-17 11:24, Jim Jagielski wrote:
Shouldn't this be 2.4.38??
On Jan 17, 2019, at 12:13 PM, Daniel Ruggeri
wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the nex
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: 87d389fca46620ac165f8d659ba0bc8180532114 *httpd-2.4.28.tar.gz
sha256: 216e3ee1dbd8d62f16155dff7a8aac7c6dbc6532954bec6cb8966a46f9819a23
*httpd-2.4.28.tar.gz
--
Daniel Ruggeri
Hi, all;
It's been a while since we've rolled a release and we've had some recent
movement, so I'd like to propose T&R of 2.4.38 in the next day or two. I'll
plan to proceed Thursday morning (US Central).
--
Daniel Ruggeri
could also maybe try moving all of the
directives to the server level and see if we may have an unexpected merge
problem.
You should at least see information about loading the key pair and what the
client-side chain looks like from SSLProxyMachineCertificateChainFile on trace8.
--
Daniel R
nners@, providing backup as I become busy
at the start of the semester.
--
Daniel Ruggeri
On November 27, 2018 8:30:51 AM CST, Rich Bowen wrote:
>Save the date: ApacheCon North America will be held in Las Vegas, at
>the
>Flamingo Hotel, September 9th through 12th, 2019. This is our 20t
cer for 10 nodes, I have an idea of tuning parameters I might set
differently than if the number of backends is in the tens of servers.
--
Daniel Ruggeri
On November 27, 2018 5:23:25 AM CST, Jim Jagielski wrote:
>In the coming week or so, I will be committing my load balance,
>load d
I like the idea. I even have a reminder in my calendar for Sunday titled "check
if release is ready to roll" :-)
I can RM again, even.
--
Daniel Ruggeri
On November 7, 2018 9:15:06 AM CST, Jim Jagielski wrote:
>Now that we have a 2.4.37 out, one in which the number of enhancemen
could be
percentage of memory used. Still yet, other servers may decide based on number
of idle GPUs on-system. I think this is roughly the same you are suggesting,
Jim J, but I struggle to think of a universal benchmark because backends are so
varied.
--
Daniel Ruggeri
On October 30, 2018 7:53:20
On 2018-10-23 14:04, Ruediger Pluem wrote:
On 10/22/2018 04:08 PM, Daniel Ruggeri wrote:
On 2018-10-18 09:36, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the
Hi, Cory;
Yes, you are correct. This gets cleaned up as part of the final
fixups in the release scripts. It's one of the things done at the last
moment :-)
--
Daniel Ruggeri
On 2018-10-22 10:23, Cory McIntire wrote:
Just a note, the date here is Sept instead of Oct :)
On 2018-10-18 09:36, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.37:
[ ] +1: It's not just good,
les/http2.t (revision 1844483)
> +++ t/modules/http2.t (working copy)
> @@ -25,6 +25,16 @@
> my $openssl_version = Net::SSLeay::OPENSSL_VERSION_NUMBER();
> if ($openssl_version < 0x1000) {
> $tls_modern = 0;
> +} else {
> + Apache::TestRequest::scheme("https");
> + my $url = '/test_ssl_version_lookup';
> + my $r = GET("$url");
> + $openssl_version = $r->content;
> + print STDOUT "OpenSSL version '$openssl_version'\n";
> + # OpenSSL/0.9.8zh, OpenSSL/1.0.2p etc.
> + if ($openssl_version =~ /\/0\./) {
> + $tls_modern = 0;
> + }
> }
>
> Apache::TestRequest::module("http2");
>
> What do people think? Should I apply it?
>
> Regards,
>
> Rainer
+1
--
Daniel Ruggeri
On 2018-10-18 09:36, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.37:
[ ] +1: It's not just good,
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: b0521606d1df54bb425adcdecf6348f126aa352c *httpd-2.4.37.tar.gz
sha256: aa97a834a32d51974be8d8a013b561e28d327387cb1da2c3c2762acd0146aabd
*httpd-2.4.37.tar.gz
--
Daniel Ruggeri
On 2018-10-18 07:12, Rainer Jung wrote:
Am 17.10.2018 um 13:41 schrieb Daniel Ruggeri:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to
2.4.x, I would like to tag the next version of our venerable server
soon.
I have already successfully completed the test suite
On 2018-10-17 13:13, Dennis Clarke wrote:
On 10/17/2018 07:41 AM, Daniel Ruggeri wrote:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to
2.4.x, I would like to tag the next version of our venerable server
soon.
I have already successfully completed the test suite
ier to
entry for an RM and we can add to the list of ready volunteers. Indeed, I was
encouraging jchampion at ACNA to toss his hat in the ring as an RM... here's to
hoping :-)
--
Daniel Ruggeri
On October 15, 2018 9:10:13 AM CDT, William A Rowe Jr
wrote:
>Like my beg for getting us
etected in [1].
Feeling good about this one :-)
How about roughly 24 hours from now?
[1]
https://lists.apache.org/thread.html/48de97bd66ceabcf84a3719b36cd69274cb8c4b64d68c46696beb906@
--
Daniel Ruggeri
Thank you so much for your thorough work.
One of these days I'd love to hear all about your testing setup. It would so
cool to run something similar on our buildbot!
--
Daniel Ruggeri
On October 17, 2018 3:01:11 AM CDT, Rainer Jung wrote:
>Thanks.
>
>I'm doing new builds
read.html/cff9db75d9e281f116382f090b3079dedc2c9842192d213ae4948e15@%3Cdev.httpd.apache.org%3E
--
Daniel Ruggeri
On 2018/10/10 19:18:45, Daniel Ruggeri wrote:
> Hi, all;
> Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
&
this release, I want to be sure
the topic gets due attention.
--
Daniel Ruggeri
On October 14, 2018 4:44:04 PM CDT, "Helmut K. C. Tessarek"
wrote:
>On 2018-10-10 15:18, Daniel Ruggeri wrote:
>> Hi, all;
>> Please find below the proposed release tarball
w how to work around this in the test suite. If we had an >
> external curl or similar available it would work. Or if we would code >
> ourselves sending a raw request on the socket and reading the raw request.>
>
> Depending on timing the test could break even for small POST sizes. Eg. >
> on my Solaris system it already breaks around 128KB, but theoretically >
> it could happen even much earlier.>
>
> Regards,>
>
> Rainer>
>
This is an issue only with LWP? I thought you also detected browsers and curl
failing with the test server as-configured?
--
Daniel Ruggeri
)
machine: x86_64
libraries:
openssl: "1.1.1"
openldap: "2.4.46"
apr: "1.6.5"
apr-util: "1.6.1"
iconv: "1.2.2"
brotli: "1.0.6"
nghttp2: "1.34.0"
zlib: "1.2.11"
pcre: "8.42"
aborting the release
process.
--
Daniel Ruggeri
7;s have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: e40e7a879b84df860215b8a80f2a535534a1c4b4 *httpd-2.4.36.tar.gz
sha256: ef788fb7c814acb2506a8b758a1a3f91f368f97bd4e6db16e98001f468e8e288
*httpd-2.4.36.tar.gz
--
Daniel Ruggeri
On 2018-10-10 07:30, Joe Orton wrote:
On Tue, Oct 09, 2018 at 03:29:49PM -0500, Daniel Ruggeri wrote:
Hi, all;
I ran through my usual testing routine, this time with OpenSSL
1.1.1, but
found several test failures. In the past, these issues have been
isolated to
my environment so I just
11"
pcre: "8.42"
libxml2: "2.9.8"
php: "5.6.38"
lua: "5.3.5"
curl: "7.61.1"
Anything look obviously crazy/wrong?
--
Daniel Ruggeri
On 2018-10-09 06:36, Daniel Ruggeri wrote:
Hi, all;
Barring any major disagreement in the next several hours, I intend to
T&R our next version later today or early tomorrow.
Hooray for TLS 1.3!
--
Daniel Ruggeri
Hi, all;
Barring any major disagreement in the next several hours, I intend to T&R our
next version later today or early tomorrow.
Hooray for TLS 1.3!
--
Daniel Ruggeri
Actually, I'm glad you asked. I committed after 2.4.35 to T&R 2.4.36 soon
after. I'm happy to do that ASAP if there are no objections.
What say you, fellow devs? How about next week?
--
Daniel Ruggeri
On October 6, 2018 7:53:58 PM CDT, Michael-Fever wrote:
>
>Aww, all I c
nstead of a
multi-to message since that seems like the easiest approach.
--
Daniel Ruggeri
On 9/28/2018 9:13 PM, William A Rowe Jr wrote:
> Sebb thank you for your analysis!
>
> Two issues; one, the reply-to field of security announcements was set
> to security@, and this is in direc
1 - 100 of 426 matches
Mail list logo