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

docs: Adding tls document describing what we support #669

Merged
merged 4 commits into from
Jan 9, 2020
Merged

Conversation

jebrando
Copy link
Collaborator

@jebrando jebrando commented Jan 9, 2020

Checklist

Reference/Link to the issue solved with this PR (if any)

Description of the problem

Description of the solution

Copy link
Contributor

@anthonyvercolano anthonyvercolano left a comment

Choose a reason for hiding this comment

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

:shipit:

@ericmitt
Copy link
Contributor

ericmitt commented Jan 9, 2020

typo: should be connection
#Resolved

@ericmitt
Copy link
Contributor

ericmitt commented Jan 9, 2020

How a customer can force node to use tls1.2 ? Is it possible at 'node runtime' level like Java, or node just use what the OS provide? The doc should explain that. #Resolved

@jebrando
Copy link
Collaborator Author

jebrando commented Jan 9, 2020

This can not be done without a code change to the underlying TLS library. So we are submitting a PR to the MQTT library that we're using.


In reply to: 572325484 [](ancestors = 572325484)

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.

3 participants