Re: announcing freenginx.org

2024-02-14 Thread Manuel
Good Evening Maxim, thank you for the work. I am speechless. My personal opinion: @F5 get an advisor for open source and maybe read something about enshittification m( TT Will follow freenginx then. Thx. > Am 14.02.2024 um 18:59 schrieb Maxim Dounin : > > Hello! > > As you probably know, F

Re: announcing freenginx.org

2024-02-14 Thread Jore
Thank you all for all your great work!!! ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx

Re: announcing freenginx.org

2024-02-14 Thread Jeffrey Walton
On Wed, Feb 14, 2024 at 12:59 PM Maxim Dounin wrote: > > 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

Re: announcing freenginx.org

2024-02-14 Thread Maxim Dounin
Hello! On Wed, Feb 14, 2024 at 07:32:48PM +, agill--- via nginx wrote: > Is there a way for us to also financially support the project or > is it going under the umbrella of a funder? Thanks for the suggestion. For now, I have enough resources to support the project and myself. -- Maxim

Re: announcing freenginx.org

2024-02-14 Thread Maxim Dounin
Hello! On Thu, Feb 15, 2024 at 03:24:59AM +0800, Jeffrey 'jf' Lim wrote: > On Thu, Feb 15, 2024 at 1:59 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 wi

Re: announcing freenginx.org

2024-02-14 Thread Jeffrey 'jf' Lim
On Thu, Feb 15, 2024 at 1:59 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

announcing freenginx.org

2024-02-14 Thread Maxim Dounin
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, fo

nginx security advisory (CVE-2024-24989, CVE-2024-24990)

2024-02-14 Thread Sergey Kandaurov
Two security issues were identified in nginx HTTP/3 implementation, which might allow an attacker that uses a specially crafted QUIC session to cause a worker process crash (CVE-2024-24989, CVE-2024-24990) or might have potential other impact (CVE-2024-24990). The issues affect nginx compiled with

nginx-1.25.4

2024-02-14 Thread Sergey Kandaurov
Changes with nginx 1.25.414 Feb 2024 *) Security: when using HTTP/3 a segmentation fault might occur in a worker process while processing a specially crafted QUIC session (CVE-2024-24989, CVE-2024-24990). *) Bugfix: connections with pe

Re: ngx_http_v3_init_session function

2024-02-14 Thread Clima Gabriel
Thanks you On Fri, Feb 9, 2024 at 1:58 PM Roman Arutyunyan wrote: > Hi Gabriel, > > On Wed, Feb 07, 2024 at 03:34:42PM +0200, Clima Gabriel wrote: > > Hello Roman, > > Thank you. Noted about the mailing list. > > > > > > My function will be called from / inline in ngx_http_ssl_servername. > > ng