chore: bump APISIX-Runtime to 1.3.17 - #13866
Closed
nic-6443 wants to merge 1 commit into
Closed
Conversation
1.3.17 builds against apisix-nginx-module 1.19.10, which makes `upstream.set_ssl_trusted_store()` take effect without a client certificate (api7/apisix-nginx-module#126) - `upstream.tls.ca_certs` in apache#13863 depends on it - and picks up ngx_http_ffi_client v0.1.2/v0.1.3.
Member
Author
|
Folding this into #13863 instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bumps
APISIX_RUNTIMEto 1.3.17, along with the version guard and the twoapisix-runtime-debugchecksums inci/linux-install-openresty.sh.1.3.17 changes two components relative to 1.3.16:
ngx_http_apisix_set_upstream_ssl()used to apply the caller-supplied trusted store only inside itsctx->upstream_cert != NULLbranch, soupstream.set_ssl_trusted_store()was silently dropped without mTLS. nginx loadsproxy_ssl_trusted_certificateinto the SSL_CTX only whenproxy_ssl_verifyis on at configuration time, which APISIX never sets, so such a caller ended up with an empty trust store. This is whatupstream.tls.ca_certsin feat(upstream): verify the upstream certificate against configurable CAs #13863 needs in order to work on its own.lua_ssl_trusted_certificate, and names resolve through a resolver installed by the host application.Checksums were taken from the published release artifacts:
Which issue(s) this PR fixes:
N/A
Checklist
The whole test suite runs against the new runtime, which is the coverage a version bump can have; there is nothing to document.