Add check_server_cert.sh #110
Conversation
| die "could not find json config file: $CONFIG" | ||
| fi | ||
|
|
||
| HOSTNAME=$(jq -r ".hostname" "$CONFIG") |
There was a problem hiding this comment.
Should this be .host?
fleet-telemetry/config/config.go
Line 31 in 613041e
| HOSTNAME=$(jq -r ".hostname" "$CONFIG") | |
| HOSTNAME=$(jq -r ".host" "$CONFIG") |
There was a problem hiding this comment.
@SirArkimedes thanks for the feedback, but this script is for validating server setup is compatible with a proposed vehicle config (which uses "hostname"). I've updated the README, and error messaging.
| fi | ||
|
|
||
| HOSTNAME=$(jq -r ".hostname" "$CONFIG") | ||
| CA=$(jq -r ".ca" "$CONFIG") |
There was a problem hiding this comment.
Should this be .ca_file?
fleet-telemetry/config/config.go
Line 131 in 613041e
| CA=$(jq -r ".ca" "$CONFIG") | |
| CA=$(jq -r ".ca_file" "$CONFIG") |
There was a problem hiding this comment.
No, that's the server config. This script accepts a fleet telemetry client config.
There was a problem hiding this comment.
Ohhhh. Okay, the new README updates make this make sense, then! Thanks!
aaronpkahn
force-pushed
the
akahn/check_csrs
branch
from
7aa2656
to
f08040a
Compare
Description
Adds a script
tools/check_server_cert.shto validate client configs against telemetry servers.Type of change
Please select all options that apply to this change:
Checklist: