CBW driver enhancements #41
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The HTTPS patch affects all protocols, not just CBW. Specifically, this impacts CAP, MSG_FEED, and ClearGuide, which all use https. Does the newer CBW firmware not allow unencrypted HTTP connections? On public networks, certificates must be checked to prevent man-in-the-middle attacks. Maybe there could be a method to allow invalid certificates on a CommLink (or protocol) level? Alternatively, we could explore adding the CBW certificate root as a trusted cert on the IRIS host. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for new firmware, https authentication, voltage and SN displayed on controller Status Tab