Skip to content
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

Upstream MQTTS without client certificate #15

Merged

Conversation

joshuastorch
Copy link
Contributor

@joshuastorch joshuastorch commented Aug 3, 2023

The original implementation did not allow to establish an upstream connection without providing a client certificate resulting in
FATAL server: loadkeys: tls: failed to find any PEM data in certificate input.
As the implementation that I tested did not support client certificates I made them optional for the upstream connection.

@joshuastorch joshuastorch changed the title Upstream MQTTS without Client Certificate Upstream MQTTS without client certificate Aug 3, 2023
@windBlaze
Copy link
Contributor

Hi @joshuastorch , thank you very much for the pull request :) Apologies for the late reaction, I was on holiday last week. Looks good, I'll take a closer look & do a quick test tomorrow, then merge it!

Copy link
Contributor

@windBlaze windBlaze left a comment

Choose a reason for hiding this comment

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

Feat approved :) New code is more flexible & the initialization and configuration of the TLS config is more straightforward. Thank you very much @joshuastorch !

@windBlaze windBlaze merged commit 6f1d0ff into NVISOsecurity:master Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants