QUIC docs with php-fpm & ssl cache

2023-05-26 Thread PGNet Dev
I've installed v1.25 nginx -V nginx version: nginx/1.25.0 (Local Build) built with OpenSSL 3.0.8 7 Feb 2023 TLS SNI support enabled configure arguments: --with-debug ... --with-http_v2_module --with-h

Re: nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

2023-04-26 Thread PGNet Dev
GCC 13 is not released yet, right? "Real Soon Now (tm)" fyi, https://gcc.gnu.org/gcc-13 April 26, 2023 The GCC developers are pleased to announce the release of GCC 13.1. ___ nginx-devel mailing list nginx-devel@nginx.org ht

Re: nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

2023-04-18 Thread PGNet Dev
GCC 13 is not released yet, right? "Real Soon Now (tm)" GCC 13.0.1 Status Report (2023-04-17) https://gcc.gnu.org/pipermail/gcc/2023-April/241140.html It's in the Fedora 38 release, which dropped today: Fedora 38 Released With GNOME 44 Desktop, GCC 13, Many New Features

nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

2023-04-18 Thread PGNet Dev
I'm building nginx mainline v1.24 on Fedora. on F37, with gcc 12, gcc --version gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4) Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions. T

Re: nginx 1.21.5 + PCRE2 build fail @ naxsi

2021-12-28 Thread PGNet Dev
On 12/28/21 13:14, Maxim Dounin wrote: The NAXSI bug mentioned in the second commit needs to be fixed before it will be possible to build NAXSI with PCRE2. Noted, & mentioned @ upstream bug (afaict, no prior relevant bug ?) thanks! fwiw, without naxsi, nginx 1.21.5 + pcre2 fails also @ ngx_ht

nginx 1.21.5 + PCRE2 build fail @ naxsi

2021-12-28 Thread PGNet Dev
with pcre2 enabled for new-version build, builds with naxsi now fail i'd reported @ naxsi upstream issue, https://github.com/nbs-system/naxsi/issues/580 comment there suggests, "Possibly connected commits: nginx/nginx@931acbf nginx/nginx@d5f1f16 (mentions NAXSI) nginx/nginx@c6fe

Re: nginx 1.19.7 + njs {0.5.0/0.5.1/HEAD} fail for Fedora 34; ok for Fedora 33. gcc version? (F33 -> 10x, F34 -> 11x)

2021-02-22 Thread PGNet Dev
On 2/22/21 12:20 PM, Dmitry Volyntsev wrote: No, it is not. Feel free to report it on Github. +1 -> https://github.com/nginx/njs/issues/376 ___ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel

nginx 1.19.7 + njs {0.5.0/0.5.1/HEAD} fail for Fedora 34; ok for Fedora 33. gcc version? (F33 -> 10x, F34 -> 11x)

2021-02-22 Thread PGNet Dev
i'm re-building nginx 1.19.7 @ fedora's COPR buildsys, enabling Fedora 34 builds, in addition to (current) Fedora 33 builds, https://copr.fedorainfracloud.org/coprs/pgfed/nginx-mainline/build/2013618/ builds with any of njs release tag 0.5.0, 0.5.1 or HEAD are fine for Fedora 33 -- no

Re: TLS1.3

2019-07-18 Thread PGNet Dev
On 7/18/19 1:15 PM, Thomas Ward wrote: Might be helpful to point at https://trac.nginx.org/nginx/ticket/1654#comment:2 and other issues which have spurned the request to rebuild downstream. Which, given that NGINX built against 1.1.0 downstream and OpenSSL downstream in Ubuntu with 1.1.1 is s

Re: TLS1.3

2019-07-18 Thread PGNet Dev
On 7/18/19 1:01 PM, Thomas Ward wrote: There's a few considerations here.  We need to make certain that such a rebuild to allow NGINX to control TLS 1.3 protocol or ciphers isn't going to introduce any additional TLS1.3 behaviors or feature functionality that otherwise would not be controlled b

effect of bcrypt hash $cost on HTTP Basic authentication's login performance?

2019-06-29 Thread PGNet Dev
When generating hashed data for "HTTP Basic" login auth protection, using bcrypt as the hash algorithm, one can vary the resultant hash strength by varying specify bcrypt's $cost, e.g. php -r "echo password_hash('$my_pass', PASSWORD_BCRYPT, ['cost' => $cost]) . PHP_EOL;" Of course, inc

Re: PCRE2 support?

2019-01-24 Thread PGNet Dev
Well, this depends on your point of view. If a project which actually developed the library fails to introduce support to the new version of the library - for an external observer this suggests that there is something wrong with the new version. FUD 'suggestions' simply aren't needed. The Exim

Re: nginx/1.13.9 + njs/head build : ngx_http_js_module.so: undefined symbol

2018-02-20 Thread PGNet Dev
On 2/20/18 1:26 PM, Dmitry Volyntsev wrote: Thank you for reporting the problem. Please, make sure that you do 'make clean’ in njs directory after hg update. Of course. I'm always hg update --clean tip r450 is reproducibly causing the error. r446 is fine atm. __

Re: nginx/1.13.9 + njs/head build : ngx_http_js_module.so: undefined symbol

2018-02-20 Thread PGNet Dev
On 2/20/18 11:41 AM, PGNet Dev wrote: cd /usr/local/src/njs/nginx hg log | head changeset: 450:757271547b56 tag: tip user:Dmitry Volyntsev date:Tue Feb 20 19:12:55 2018 +0300

nginx/1.13.9 + njs/head build : ngx_http_js_module.so: undefined symbol

2018-02-20 Thread PGNet Dev
Upgrading nginx 1.13.8 -> 1.13.9 with usual ./configure \ ... \ --add-dynamic-module=/usr/local/src/njs/nginx and cd /usr/local/src/njs/nginx hg log | head changeset: 450:757271547b56 tag: tip user:

Re: [njs] Version 0.1.12. DOC BUG

2017-08-13 Thread PGNet Dev
fyi, site doc bug/typo instructions @ http://nginx.org/en/docs/njs_about.html state ... The modules can also be built as dynamic: ./configure --add-dynamic_module=path-to-njs/nginx ... that's a typo. should be, ./configure --add-dynam

Re: nginx 1.11.3 build, linking openssl 1.1.0 (beta/pre-6) fails @ ‘SSL_R_NO_CIPHERS_PASSED’

2016-08-11 Thread PGNet Dev
On 08/11/2016 09:33 AM, Valentin V. Bartenev wrote: On Thursday 11 August 2016 08:51:40 pgndev wrote: This was already fixed a few days ago. http://hg.nginx.org/nginx/rev/1891b2892b68 wbr, Valentin V. Bartenev Didn't see that / Applies cleanly to 1.11.3 release, nginx -V nginx versi