feat(mxgw-go): add -require-certificate-validation for strict TLS (#199)
Over TLS without -ca-cert the CLI was always skip-verify, with no way to ask for verification against the system roots even though the library supports it. The new common flag is wired to Options.RequireCertificateValidation in both the gateway and Galaxy dialers and echoed in the redacted JSON options. Test: tls_flag_test.go starts a self-signed TLS gRPC gateway; the default open-session succeeds (positive control) and the same call with the flag fails to dial (fails on the old code with 'flag provided but not defined').
This commit is contained in:
@@ -432,7 +432,11 @@ the gateway:
|
||||
|
||||
Every subcommand wired into the CLI. All accept the common flags
|
||||
(`-endpoint`, `-plaintext`, `-api-key` / `-api-key-env`, `-ca-cert`,
|
||||
`-server-name-override`, `-call-timeout`) and most accept `-json`.
|
||||
`-server-name-override`, `-call-timeout`, `-require-certificate-validation`) and
|
||||
most accept `-json`. Over TLS without `-ca-cert` the CLI accepts any gateway
|
||||
certificate (the self-signed default); `-require-certificate-validation` sets
|
||||
`Options.RequireCertificateValidation` so the certificate must chain to the
|
||||
system trust roots instead.
|
||||
|
||||
| Command | Purpose |
|
||||
|---|---|
|
||||
|
||||
Reference in New Issue
Block a user