RE: nginx 1.18.0 implicitly enables TLS 1.3 (with only "ssl_protocols TLSv1.2; " in nginx.conf config)

2020-11-29 Thread Thomas Ward
We had this problem in Ubuntu's repos until we rebuilt against newer OpenSSL and the TLS 1.3 variables were exposed to NGINX at build time - then you could turn it off in ssl_protocols by not specifying TLSv1.3.However, your case indicates that you are linked (compiled) against older LibreSSL th

nginx 1.18.0 implicitly enables TLS 1.3 (with only "ssl_protocols TLSv1.2; " in nginx.conf config)

2020-11-29 Thread nginx
Hello, I've noticed that nginx 1.18.0 always enables TLS 1.3 even if not configured to do so. I've observed this behavior on OpenBSD with (nginx 1.18.0 linked against LibreSSL 3.3.0) and on Ubuntu 20.04 (nginx 1.18.0 linked against OpenSSL 1.1.1f). I don't know which release of nginx introduc

empty variable in access log

2020-11-29 Thread Frank Liu
Hi, If I create a variable, default to blank: map upstream_env $upstream_env { default ""; } and log it in access log (log_format has $upstream_env). I see a "-" in the log file, which is as expected, but for a 2-way SSL virtual host, I don't see the "-", just blank. Is that a bug?