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.
This extends database connection a little:
tls_servername
option. This can be used withsslmode: verify-full
when the hostname does not match the TLS certificate name, for example when connecting to a specific IP. This is not relevant forsslmode: disable
orsslmode: verify-ca
, since neither of those verify the hostname.reject_ip_ranges: [...]
support to all connections, to avoid connecting to specific hosts. The implementation does not check all cases for MongoDB and MySQL yet, but combined enforced TLS, this should be fairly effective.client_auth.block_local_jwks
option now accepts an array of ranges. This means we now also support IPv6-only servers for the JWKS URI.This required a bit of restructuring to the connection libs. I also restructured things a bit to improve internal dependencies: the jpgwire package no longer depends on sync-rules or service-types.
The implementation of blocking IP ranges operates on two levels:
lookup
function used for DNS lookups. This is the same as the normal lookup, except it now validates the IP ranges.