Skip to content

Conversation

@kares
Copy link
Contributor

@kares kares commented Jan 25, 2022

Adds ssl_verification_mode configuration option, with the default being 'full'.
Manticore wise, due backwards compatibility, the 'full' option translates to verify: :strict.
This could be relaxed in the future (verify: :browser) but would need more investigation/implementation whether we could force SAN to be present in the server certificate (same way as ES/Beats implement strict verification).


closing #31 (alternate impl)
closing #34 (alternate impl)

@kares kares linked an issue Jan 25, 2022 that may be closed by this pull request
@kares kares self-assigned this Jan 25, 2022
Copy link
Member

@jsvd jsvd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nit picks to improve reading comprehension when tests fail, otherwise LGTM
next step is going to plugins that use this and adding documentation snippet for this new setting.
The direction we want to go is to group this mixin and the plugins that use it (http output, http poller) into an integration, to avoid this finicky weak link between plugins and mixins.


case @ssl_verification_mode
when 'full'
# NOTE: would make sense to have :browser here but historically we've used the (:strict) default
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll also want to have something like "certificate" for a mode that verifies the cert chain but doesn't perform hostname verification. Totally out of scope for this PR though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add flag to disable strict SSL hostname verifification

2 participants