Aapo Talvensaari
Aapo Talvensaari
@freeyoung, I need to rename this first as it conflicts with `lua-resty-string`.
@shawnchapla-8451, what version of `lua-resty-session` do you have? For that library it needs to be `
On 3.10 the line is this probably this: https://github.com/bungle/lua-resty-session/blob/v3.10/lib/resty/session/ciphers/aes.lua#L101 and then you find it here: https://github.com/openresty/lua-resty-string/blob/master/lib/resty/aes.lua#L283-L285 On 4.0.3 I think it is this: https://github.com/bungle/lua-resty-session/blob/v4.0.3/lib/resty/session/utils.lua#L713 `lua-resty-openssl` seems to use different APIs:...
@xiangnanscu, I am not aware of it. Contributions are welcomed.
This feels like small but potentially breaking change. 1. we allow "invalid" configurations currently and then can be stored in database 2. we make our validations more correct BUT restricting,...
Since this has been so long in a products, do we consider this as a `fix`. It seems like a potentially breaking change? @hbagdi, @kikito?
@hanshuebner, do you have an idea why this might be happening? Is opentelemetry plugin also configured through kong.conf? I do not know this code too well.
Yes, the observation is not correct, see: https://github.com/Kong/kong/blob/master/kong/conf_loader/init.lua#L438
``` KONG_SSL_PROTOCOLS="TLSv1.3" \ KONG_NGINX_HTTP_SSL_PROTOCOLS="TLSv1.3" \ kong prepare ``` ``` cat /usr/local/kong/nginx-kong.conf | grep ssl_protocols ``` ``` ssl_protocols TLSv1.2 TLSv1.3; ``` Also on `intermediate` (the default) the TLSv1.1 is not enabled,...
Internal ticket: KAG-3280