-
Notifications
You must be signed in to change notification settings - Fork 7
MEN-8351: fix(build): Set default value for secondary CA cert to false + misc #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
MEN-8351: fix(build): Set default value for secondary CA cert to false + misc #207
Conversation
Signed-off-by: Lluis Campos <[email protected]>
Ticket: MEN-8351 Signed-off-by: Lluis Campos <[email protected]>
The secondary CA cert is really optional, as a custom Mender Server could use the same domain for both API calls and Artifacts storage. Set `MENDER_NET_CA_CERTIFICATE_TAG_SECONDARY_ENABLED` default to `n` and instead select it when selecting hosted Mender option(s). Ticket: MEN-8351 Signed-off-by: Lluis Campos <[email protected]>
ee4aacf
to
092a79f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me otherwise.
@@ -469,7 +469,7 @@ if MENDER_MCU_CLIENT | |||
range 0 2 | |||
default 2 | |||
help | |||
Peer verification level for TLS connection. | |||
Peer verification level for TLS connection. For testing purposes, set to 0 to skip TLS peer verify |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So what does 1
mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO we don't really support "optional", because to properly use it we would need to check the handshake result and print a warning or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. The help
should say it then. And perhaps create a task to make sure 1
is handled gracefully?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
The secondary CA cert is really optional, as a custom Mender Server could use the same domain for both API calls and Artifacts storage.
Set
MENDER_NET_CA_CERTIFICATE_TAG_SECONDARY_ENABLED
default ton
and instead select it when selecting hosted Mender option(s).