From mdounin at mdounin.ru Wed Feb 14 18:03:11 2024
From: mdounin at mdounin.ru (Maxim Dounin)
Date: Wed, 14 Feb 2024 21:03:11 +0300
Subject: announcing freenginx.org
Message-ID:
Hello!
As you probably know, F5 closed Moscow office in 2022, and I no
longer work for F5 since then. Still, we?ve reached an agreement
that I will maintain my role in nginx development as a volunteer.
And for almost two years I was working on improving nginx and
making it better for everyone, for free.
Unfortunately, some new non-technical management at F5 recently
decided that they know better how to run open source projects. In
particular, they decided to interfere with security policy nginx
uses for years, ignoring both the policy and developers? position.
That?s quite understandable: they own the project, and can do
anything with it, including doing marketing-motivated actions,
ignoring developers position and community. Still, this
contradicts our agreement. And, more importantly, I no longer able
to control which changes are made in nginx within F5, and no longer
see nginx as a free and open source project developed and
maintained for the public good.
As such, starting from today, I will no longer participate in nginx
development as run by F5. Instead, I?m starting an alternative
project, which is going to be run by developers, and not corporate
entities:
http://freenginx.org/
The goal is to keep nginx development free from arbitrary corporate
actions. Help and contributions are welcome. Hope it will be
beneficial for everyone.
--
Maxim Dounin
http://freenginx.org/
From serg.brester at sebres.de Wed Feb 14 21:45:37 2024
From: serg.brester at sebres.de (Sergey Brester)
Date: Wed, 14 Feb 2024 22:45:37 +0100
Subject: announcing freenginx.org
In-Reply-To:
References:
Message-ID: <6c0cfb0380b84175709b1bd80ba27397@sebres.de>
Hi Maxim,
it is pity to hear such news...
I have few comments and questions about, which I enclosed inline
below...
Regards,
Serg.
14.02.2024 19:03, Maxim Dounin wrote:
> Hello!
>
> As you probably know, F5 closed Moscow office in 2022, and I no
> longer work for F5 since then. Still, we've reached an agreement
> that I will maintain my role in nginx development as a volunteer.
> And for almost two years I was working on improving nginx and
> making it better for everyone, for free.
And you did a very good job!
> Unfortunately, some new non-technical management at F5 recently
> decided that they know better how to run open source projects. In
> particular, they decided to interfere with security policy nginx
> uses for years, ignoring both the policy and developers' position.
Can you explain a bit more about that (or provide some examples
or a link to a public discussion about, if it exists)?
> That's quite understandable: they own the project, and can do
> anything with it, including doing marketing-motivated actions,
> ignoring developers position and community. Still, this
> contradicts our agreement. And, more importantly, I no longer able
> to control which changes are made in nginx within F5, and no longer
> see nginx as a free and open source project developed and
> maintained for the public good.
Do you speak only about you?.. Or are there also other developers which
share your point of view? Just for the record...
What is about R. Arutyunyan, V. Bartenev and others?
Could one expect any statement from Igor (Sysoev) about the subject?
> As such, starting from today, I will no longer participate in nginx
> development as run by F5. Instead, I'm starting an alternative
> project, which is going to be run by developers, and not corporate
> entities:
>
> http://freenginx.org/ [1]
Why yet another fork? I mean why just not "angie", for instance?
Additionally I'd like to ask whether the name "freenginx" is really well
thought-out?
I mean:
- it can be easy confused with free nginx (compared to nginx plus)
- the search for that will be horrible (if you would try to search for
freenginx,
even as exact (within quotes, with plus etc), many internet search
engine
would definitely include free nginx in the result.
- possibly copyright or trademark problems, etc
> The goal is to keep nginx development free from arbitrary corporate
> actions. Help and contributions are welcome. Hope it will be
> beneficial for everyone.
Just as an idea: switch the primary dev to GH (github)... (and commonly
from hg to git).
I'm sure it would boost the development drastically, as well as bring
many new
developers and let grow the community.
Links:
------
[1] http://freenginx.org/
From mdounin at mdounin.ru Wed Feb 14 22:21:10 2024
From: mdounin at mdounin.ru (Maxim Dounin)
Date: Thu, 15 Feb 2024 01:21:10 +0300
Subject: announcing freenginx.org
In-Reply-To: <6c0cfb0380b84175709b1bd80ba27397@sebres.de>
References:
<6c0cfb0380b84175709b1bd80ba27397@sebres.de>
Message-ID:
Hello!
On Wed, Feb 14, 2024 at 10:45:37PM +0100, Sergey Brester wrote:
> Hi Maxim,
>
> it is pity to hear such news...
>
> I have few comments and questions about, which I enclosed inline below...
>
> Regards,
> Serg.
>
> 14.02.2024 19:03, Maxim Dounin wrote:
>
> > Hello!
> >
> > As you probably know, F5 closed Moscow office in 2022, and I no
> > longer work for F5 since then. Still, we've reached an agreement
> > that I will maintain my role in nginx development as a volunteer.
> > And for almost two years I was working on improving nginx and
> > making it better for everyone, for free.
>
> And you did a very good job!
Thanks.
> > Unfortunately, some new non-technical management at F5 recently
> > decided that they know better how to run open source projects. In
> > particular, they decided to interfere with security policy nginx
> > uses for years, ignoring both the policy and developers' position.
>
> Can you explain a bit more about that (or provide some examples
> or a link to a public discussion about, if it exists)?
I've already provided some details here:
https://freenginx.org/pipermail/nginx/2024-February/000007.html
: The most recent "security advisory" was released despite the fact
: that the particular bug in the experimental HTTP/3 code is
: expected to be fixed as a normal bug as per the existing security
: policy, and all the developers, including me, agree on this.
:
: And, while the particular action isn't exactly very bad, the
: approach in general is quite problematic.
There was no public discussion. The only discussion I'm aware of
happened on the security-alert@ list, and the consensus was that
the bug should be fixed as a normal bug. Still, I was reached
several days ago with the information that some unnamed management
requested an advisory and security release anyway, regardless of
the policy and developers position.
> > That's quite understandable: they own the project, and can do
> > anything with it, including doing marketing-motivated actions,
> > ignoring developers position and community. Still, this
> > contradicts our agreement. And, more importantly, I no longer able
> > to control which changes are made in nginx within F5, and no longer
> > see nginx as a free and open source project developed and
> > maintained for the public good.
>
> Do you speak only about you?.. Or are there also other developers which
> share your point of view? Just for the record...
> What is about R. Arutyunyan, V. Bartenev and others?
> Could one expect any statement from Igor (Sysoev) about the subject?
I speak only about me. Others, if they are interested in, are
welcome to join.
> > As such, starting from today, I will no longer participate in nginx
> > development as run by F5. Instead, I'm starting an alternative
> > project, which is going to be run by developers, and not corporate
> > entities:
> >
> > http://freenginx.org/ [1]
>
> Why yet another fork? I mean why just not "angie", for instance?
The "angie" fork shares the same problem as nginx run by F5: it's
run by a for-profit corporate entity. Even if it's good enough
now, things might change unexpectedly, like it happened with F5.
> Additionally I'd like to ask whether the name "freenginx" is really well
> thought-out?
> I mean:
> - it can be easy confused with free nginx (compared to nginx plus)
> - the search for that will be horrible (if you would try to search for
> freenginx,
> even as exact (within quotes, with plus etc), many internet search
> engine
> would definitely include free nginx in the result.
> - possibly copyright or trademark problems, etc
Apart from potential trademark concerns (which I believe do not
apply here, but IANAL), these does not seem to be significant (and
search results are already good enough). Still, the name aligns
well with project goals.
> > The goal is to keep nginx development free from arbitrary corporate
> > actions. Help and contributions are welcome. Hope it will be
> > beneficial for everyone.
>
> Just as an idea: switch the primary dev to GH (github)... (and commonly from
> hg to git).
> I'm sure it would boost the development drastically, as well as bring many
> new
> developers and let grow the community.
While I understand the suggestion and potential benefits, I'm not
a fun of git and github, and prefer Mercurial.
--
Maxim Dounin
http://mdounin.ru/
From vasiliy.soshnikov at gmail.com Wed Feb 14 22:33:08 2024
From: vasiliy.soshnikov at gmail.com (Vasiliy Soshnikov)
Date: Thu, 15 Feb 2024 01:33:08 +0300
Subject: announcing freenginx.org
In-Reply-To:
References:
<6c0cfb0380b84175709b1bd80ba27397@sebres.de>
Message-ID:
Hello Maxim,
Sad to read it. I can't promise that, but I will try to support your
project by using freenginx at least.
I wish good luck to freenginx!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mdounin at mdounin.ru Wed Feb 14 22:35:29 2024
From: mdounin at mdounin.ru (Maxim Dounin)
Date: Thu, 15 Feb 2024 01:35:29 +0300
Subject: announcing freenginx.org
In-Reply-To:
References:
<6c0cfb0380b84175709b1bd80ba27397@sebres.de>
Message-ID:
Hello!
On Thu, Feb 15, 2024 at 01:33:08AM +0300, Vasiliy Soshnikov wrote:
> Hello Maxim,
> Sad to read it. I can't promise that, but I will try to support your
> project by using freenginx at least.
> I wish good luck to freenginx!
Thanks, appreciated.
--
Maxim Dounin
http://mdounin.ru/
From archimedes.gaviola at gmail.com Thu Feb 15 08:49:10 2024
From: archimedes.gaviola at gmail.com (Archimedes Gaviola)
Date: Thu, 15 Feb 2024 16:49:10 +0800
Subject: announcing freenginx.org
In-Reply-To:
References:
Message-ID:
On Thu, Feb 15, 2024 at 2:03?AM Maxim Dounin wrote:
> Hello!
>
> As you probably know, F5 closed Moscow office in 2022, and I no
> longer work for F5 since then. Still, we?ve reached an agreement
> that I will maintain my role in nginx development as a volunteer.
> And for almost two years I was working on improving nginx and
> making it better for everyone, for free.
>
> Unfortunately, some new non-technical management at F5 recently
> decided that they know better how to run open source projects. In
> particular, they decided to interfere with security policy nginx
> uses for years, ignoring both the policy and developers? position.
>
> That?s quite understandable: they own the project, and can do
> anything with it, including doing marketing-motivated actions,
> ignoring developers position and community. Still, this
> contradicts our agreement. And, more importantly, I no longer able
> to control which changes are made in nginx within F5, and no longer
> see nginx as a free and open source project developed and
> maintained for the public good.
>
> As such, starting from today, I will no longer participate in nginx
> development as run by F5. Instead, I?m starting an alternative
> project, which is going to be run by developers, and not corporate
> entities:
>
> http://freenginx.org/
>
> The goal is to keep nginx development free from arbitrary corporate
> actions. Help and contributions are welcome. Hope it will be
> beneficial for everyone.
>
>
> --
> Maxim Dounin
> http://freenginx.org/
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx-devel
Hi Maxim,
Sorry to hear that. Is the license still the same for freenginx?
Thanks,
Archimedes
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From antoine.bonavita at gmail.com Thu Feb 15 09:40:05 2024
From: antoine.bonavita at gmail.com (Antoine Bonavita)
Date: Thu, 15 Feb 2024 10:40:05 +0100
Subject: announcing freenginx.org
In-Reply-To:
References:
Message-ID:
Maxim,
Thanks for the amazing work and your dedication all those years.
Will definitely follow freenginx and use it as my webserver of choice.
A.
On Thu, Feb 15, 2024 at 9:49?AM Archimedes Gaviola <
archimedes.gaviola at gmail.com> wrote:
>
>
> On Thu, Feb 15, 2024 at 2:03?AM Maxim Dounin wrote:
>
>> Hello!
>>
>> As you probably know, F5 closed Moscow office in 2022, and I no
>> longer work for F5 since then. Still, we?ve reached an agreement
>> that I will maintain my role in nginx development as a volunteer.
>> And for almost two years I was working on improving nginx and
>> making it better for everyone, for free.
>>
>> Unfortunately, some new non-technical management at F5 recently
>> decided that they know better how to run open source projects. In
>> particular, they decided to interfere with security policy nginx
>> uses for years, ignoring both the policy and developers? position.
>>
>> That?s quite understandable: they own the project, and can do
>> anything with it, including doing marketing-motivated actions,
>> ignoring developers position and community. Still, this
>> contradicts our agreement. And, more importantly, I no longer able
>> to control which changes are made in nginx within F5, and no longer
>> see nginx as a free and open source project developed and
>> maintained for the public good.
>>
>> As such, starting from today, I will no longer participate in nginx
>> development as run by F5. Instead, I?m starting an alternative
>> project, which is going to be run by developers, and not corporate
>> entities:
>>
>> http://freenginx.org/
>>
>> The goal is to keep nginx development free from arbitrary corporate
>> actions. Help and contributions are welcome. Hope it will be
>> beneficial for everyone.
>>
>>
>> --
>> Maxim Dounin
>> http://freenginx.org/
>> _______________________________________________
>> nginx-devel mailing list
>> nginx-devel at nginx.org
>> https://mailman.nginx.org/mailman/listinfo/nginx-devel
>
>
> Hi Maxim,
>
> Sorry to hear that. Is the license still the same for freenginx?
>
> Thanks,
> Archimedes
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mdounin at mdounin.ru Thu Feb 15 10:33:03 2024
From: mdounin at mdounin.ru (Maxim Dounin)
Date: Thu, 15 Feb 2024 13:33:03 +0300
Subject: announcing freenginx.org
In-Reply-To:
References:
Message-ID:
Hello!
On Thu, Feb 15, 2024 at 04:49:10PM +0800, Archimedes Gaviola wrote:
> On Thu, Feb 15, 2024 at 2:03?AM Maxim Dounin wrote:
>
> > Hello!
> >
> > As you probably know, F5 closed Moscow office in 2022, and I no
> > longer work for F5 since then. Still, we?ve reached an agreement
> > that I will maintain my role in nginx development as a volunteer.
> > And for almost two years I was working on improving nginx and
> > making it better for everyone, for free.
> >
> > Unfortunately, some new non-technical management at F5 recently
> > decided that they know better how to run open source projects. In
> > particular, they decided to interfere with security policy nginx
> > uses for years, ignoring both the policy and developers? position.
> >
> > That?s quite understandable: they own the project, and can do
> > anything with it, including doing marketing-motivated actions,
> > ignoring developers position and community. Still, this
> > contradicts our agreement. And, more importantly, I no longer able
> > to control which changes are made in nginx within F5, and no longer
> > see nginx as a free and open source project developed and
> > maintained for the public good.
> >
> > As such, starting from today, I will no longer participate in nginx
> > development as run by F5. Instead, I?m starting an alternative
> > project, which is going to be run by developers, and not corporate
> > entities:
> >
> > http://freenginx.org/
> >
> > The goal is to keep nginx development free from arbitrary corporate
> > actions. Help and contributions are welcome. Hope it will be
> > beneficial for everyone.
> >
> >
> > --
> > Maxim Dounin
> > http://freenginx.org/
>
> Hi Maxim,
>
> Sorry to hear that. Is the license still the same for freenginx?
Yes, the license will remain the same.
--
Maxim Dounin
http://mdounin.ru/
From ersjtwmb at addy.io Thu Feb 15 14:06:06 2024
From: ersjtwmb at addy.io (ersjtwmb at addy.io)
Date: Thu, 15 Feb 2024 14:06:06 +0000
Subject: Freenginx license -- copyleft would help
Message-ID: <76f6d5ad99402cff923bc8c3471a86f9@addy.io>
Hello,
One of my friends told me about what is hapenning with the nginx.
I was happy since I knew that the current model could lead to something bad.
What I was the most interested in was if the project's license hase changed.
A non-copyleft license allows a company to take everything from the upstream and add stuff to it without sharing the changes.
That is for example what happened to anonaddy.com (addy.io),
originally licensed under MIT (x11) license.
That is why I suggest that the license should be changed so that it holds some copyleft.
As a starting point I suggest the Mozilla Public License 2.0, which is considered a weak copyleft license.
I think that this aligns with the project's mission:
"[...] no longer see nginx as a free and open source project developed and maintained for the public good."
"The goal is to keep nginx development free from arbitrary corporate actions."
In my opinion the stronger the copyleft the better (MPL
References: <76f6d5ad99402cff923bc8c3471a86f9@addy.io>
Message-ID:
Hello!
On Thu, Feb 15, 2024 at 02:06:06PM +0000, ersjtwmb at addy.io wrote:
> Hello,
>
> One of my friends told me about what is hapenning with the nginx.
> I was happy since I knew that the current model could lead to something bad.
> What I was the most interested in was if the project's license hase changed.
> A non-copyleft license allows a company to take everything from the upstream and add stuff to it without sharing the changes.
> That is for example what happened to anonaddy.com (addy.io),
> originally licensed under MIT (x11) license.
>
> That is why I suggest that the license should be changed so that it holds some copyleft.
> As a starting point I suggest the Mozilla Public License 2.0, which is considered a weak copyleft license.
>
> I think that this aligns with the project's mission:
> "[...] no longer see nginx as a free and open source project developed and maintained for the public good."
> "The goal is to keep nginx development free from arbitrary corporate actions."
>
>
> In my opinion the stronger the copyleft the better (MPL
> What do you think about this?
While copyleft licenses might be beneficial to prevent
corporations from using the code without sharing improvements, I
don't think this is a concern here. As long as there are
developers who are willing to work on the project, there will be
no issues with any free license.
Also, as a long-time FreeBSD user and contributor, and I think
that BSD license is actually better from the freedom point of
view, as it does not restrict users from doing whatever they want.
--
Maxim Dounin
http://mdounin.ru/
From mdounin at mdounin.ru Mon Feb 19 00:04:06 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 03:04:06 +0300
Subject: [PATCH 0 of 4] merge from F5 nginx branch
Message-ID:
Hello!
The following patch series merges fixes from the F5 nginx branch.
I've reviewed these patches and they look good, so I'm going to
commit them shortly. Comments are welcome.
--
Maxim Dounin
From mdounin at mdounin.ru Mon Feb 19 00:04:07 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 03:04:07 +0300
Subject: [PATCH 1 of 4] QUIC: fixed unsent MTU probe acknowledgement
In-Reply-To:
References:
Message-ID: <2ed3f57dca0a664340bc.1708301047@vm-bsd.mdounin.ru>
# HG changeset patch
# User Roman Arutyunyan
# Date 1707915388 -14400
# Wed Feb 14 16:56:28 2024 +0400
# Node ID 2ed3f57dca0a664340bca2236c7d614902db4180
# Parent 73eb75bee30f4aee66edfb500270dbb14710aafd
QUIC: fixed unsent MTU probe acknowledgement.
Previously if an MTU probe send failed early in ngx_quic_frame_sendto()
due to allocation error or congestion control, the application level packet
number was not increased, but was still saved as MTU probe packet number.
Later when a packet with this number was acknowledged, the unsent MTU probe
was acknowledged as well. This could result in discovering a bigger MTU than
supported by the path, which could lead to EMSGSIZE (Message too long) errors
while sending further packets.
The problem existed since PMTUD was introduced in 58afcd72446f (1.25.2).
Back then only the unlikely memory allocation error could trigger it. However
in efcdaa66df2e congestion control was added to ngx_quic_frame_sendto() which
can now trigger the issue with a higher probability.
diff --git a/src/event/quic/ngx_event_quic_migration.c b/src/event/quic/ngx_event_quic_migration.c
--- a/src/event/quic/ngx_event_quic_migration.c
+++ b/src/event/quic/ngx_event_quic_migration.c
@@ -909,6 +909,7 @@ static ngx_int_t
ngx_quic_send_path_mtu_probe(ngx_connection_t *c, ngx_quic_path_t *path)
{
size_t mtu;
+ uint64_t pnum;
ngx_int_t rc;
ngx_uint_t log_error;
ngx_quic_frame_t *frame;
@@ -925,7 +926,7 @@ ngx_quic_send_path_mtu_probe(ngx_connect
qc = ngx_quic_get_connection(c);
ctx = ngx_quic_get_send_ctx(qc, ssl_encryption_application);
- path->mtu_pnum[path->tries] = ctx->pnum;
+ pnum = ctx->pnum;
ngx_log_debug4(NGX_LOG_DEBUG_EVENT, c->log, 0,
"quic path seq:%uL send probe "
@@ -943,14 +944,18 @@ ngx_quic_send_path_mtu_probe(ngx_connect
path->mtu = mtu;
c->log_error = log_error;
+ if (rc == NGX_OK) {
+ path->mtu_pnum[path->tries] = pnum;
+ return NGX_OK;
+ }
+
+ ngx_log_debug2(NGX_LOG_DEBUG_EVENT, c->log, 0,
+ "quic path seq:%uL rejected mtu:%uz",
+ path->seqnum, path->mtud);
+
if (rc == NGX_ERROR) {
if (c->write->error) {
c->write->error = 0;
-
- ngx_log_debug2(NGX_LOG_DEBUG_EVENT, c->log, 0,
- "quic path seq:%uL rejected mtu:%uz",
- path->seqnum, path->mtud);
-
return NGX_DECLINED;
}
@@ -976,7 +981,7 @@ ngx_quic_handle_path_mtu(ngx_connection_
pnum = path->mtu_pnum[i];
if (pnum == NGX_QUIC_UNSET_PN) {
- break;
+ continue;
}
if (pnum < min || pnum > max) {
From mdounin at mdounin.ru Mon Feb 19 00:04:08 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 03:04:08 +0300
Subject: [PATCH 2 of 4] QUIC: trial packet decryption in response to invalid
key update
In-Reply-To:
References:
Message-ID: <1bf1b423f26853d0453e.1708301048@vm-bsd.mdounin.ru>
# HG changeset patch
# User Sergey Kandaurov
# Date 1707911734 -14400
# Wed Feb 14 15:55:34 2024 +0400
# Node ID 1bf1b423f26853d0453ee30fa4ed4467ea05af7c
# Parent 2ed3f57dca0a664340bca2236c7d614902db4180
QUIC: trial packet decryption in response to invalid key update.
Inspired by RFC 9001, Section 6.3, trial packet decryption with the current
keys is now used to avoid a timing side-channel signal. Further, this fixes
segfault while accessing missing next keys (ticket #2585).
diff --git a/src/event/quic/ngx_event_quic_protection.c b/src/event/quic/ngx_event_quic_protection.c
--- a/src/event/quic/ngx_event_quic_protection.c
+++ b/src/event/quic/ngx_event_quic_protection.c
@@ -1144,8 +1144,19 @@ ngx_quic_decrypt(ngx_quic_header_t *pkt,
key_phase = (pkt->flags & NGX_QUIC_PKT_KPHASE) != 0;
if (key_phase != pkt->key_phase) {
- secret = &pkt->keys->next_key.client;
- pkt->key_update = 1;
+ if (pkt->keys->next_key.client.ctx != NULL) {
+ secret = &pkt->keys->next_key.client;
+ pkt->key_update = 1;
+
+ } else {
+ /*
+ * RFC 9001, 6.3. Timing of Receive Key Generation.
+ *
+ * Trial decryption to avoid timing side-channel.
+ */
+ ngx_log_debug0(NGX_LOG_DEBUG_EVENT, pkt->log, 0,
+ "quic next key missing");
+ }
}
}
From mdounin at mdounin.ru Mon Feb 19 00:04:09 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 03:04:09 +0300
Subject: [PATCH 3 of 4] QUIC: fixed stream cleanup (ticket #2586)
In-Reply-To:
References:
Message-ID: <4ed4e1e7f115cd48ee89.1708301049@vm-bsd.mdounin.ru>
# HG changeset patch
# User Roman Arutyunyan
# Date 1707911737 -14400
# Wed Feb 14 15:55:37 2024 +0400
# Node ID 4ed4e1e7f115cd48ee891d7cae172d5745e38e00
# Parent 1bf1b423f26853d0453ee30fa4ed4467ea05af7c
QUIC: fixed stream cleanup (ticket #2586).
Stream connection cleanup handler ngx_quic_stream_cleanup_handler() calls
ngx_quic_shutdown_stream() after which it resets the pointer from quic stream
to the connection (sc->connection = NULL). Previously if this call failed,
sc->connection retained the old value, while the connection was freed by the
application code. This resulted later in a second attempt to close the freed
connection, which lead to allocator double free error.
The fix is to reset the sc->connection pointer in case of error.
diff --git a/src/event/quic/ngx_event_quic_streams.c b/src/event/quic/ngx_event_quic_streams.c
--- a/src/event/quic/ngx_event_quic_streams.c
+++ b/src/event/quic/ngx_event_quic_streams.c
@@ -1097,6 +1097,7 @@ ngx_quic_stream_cleanup_handler(void *da
"quic stream id:0x%xL cleanup", qs->id);
if (ngx_quic_shutdown_stream(c, NGX_RDWR_SHUTDOWN) != NGX_OK) {
+ qs->connection = NULL;
goto failed;
}
From mdounin at mdounin.ru Mon Feb 19 00:04:10 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 03:04:10 +0300
Subject: [PATCH 4 of 4] Updated OpenSSL and zlib used for win32 builds
In-Reply-To:
References:
Message-ID: <0d9e536ec6283b25b8bf.1708301050@vm-bsd.mdounin.ru>
# HG changeset patch
# User Sergey Kandaurov
# Date 1707911742 -14400
# Wed Feb 14 15:55:42 2024 +0400
# Node ID 0d9e536ec6283b25b8bfb5b64bcb9ffe91de5557
# Parent 4ed4e1e7f115cd48ee891d7cae172d5745e38e00
Updated OpenSSL and zlib used for win32 builds.
diff --git a/misc/GNUmakefile b/misc/GNUmakefile
--- a/misc/GNUmakefile
+++ b/misc/GNUmakefile
@@ -6,8 +6,8 @@ TEMP = tmp
CC = cl
OBJS = objs.msvc8
-OPENSSL = openssl-3.0.11
-ZLIB = zlib-1.3
+OPENSSL = openssl-3.0.13
+ZLIB = zlib-1.3.1
PCRE = pcre2-10.39
From mdounin at mdounin.ru Mon Feb 19 13:46:45 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 16:46:45 +0300
Subject: [PATCH 0 of 5] name changes
Message-ID:
Hello!
The following patch series changes the name to "freenginx" in
some places, notably domain name in links, server identification as
returned in the Server response header, the version number as
shown in "nginx -v", in CHANGES for upcoming versions, and the name
of release tarballs (and win32 zip files).
The binary file name, configuration file name, and so on are preserved
as is, so the result can be used as a drop-in replacement for the existing
installations.
Review / comments appreciated.
--
Maxim Dounin
From mdounin at mdounin.ru Mon Feb 19 13:46:46 2024
From: mdounin at mdounin.ru (=?utf-8?q?Maxim_Dounin?=)
Date: Mon, 19 Feb 2024 16:46:46 +0300
Subject: [PATCH 1 of 5] Free nginx: changed domain to freenginx.org
In-Reply-To:
References:
Message-ID: <985b0bda403cd49580dc.1708350406@vm-bsd.mdounin.ru>
# HG changeset patch
# User Maxim Dounin
# Date 1708301479 -10800
# Mon Feb 19 03:11:19 2024 +0300
# Node ID 985b0bda403cd49580dc6bf080868f04b0ff0849
# Parent 0d9e536ec6283b25b8bfb5b64bcb9ffe91de5557
Free nginx: changed domain to freenginx.org.
diff --git a/docs/html/index.html b/docs/html/index.html
--- a/docs/html/index.html
+++ b/docs/html/index.html
@@ -14,9 +14,7 @@ font-family: Tahoma, Verdana, Arial, san
working. Further configuration is required.
For online documentation and support please refer to
-nginx.org.
-Commercial support is available at
-nginx.com.
+freenginx.org.
Thank you for using nginx.