Fix login on new firmware #127
Merged
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
QuantumEntangledAndy
changed the title
|
It seems the new firmware won't accept the 0x02 encryption algorithm and is now using just 0x12. I will have to work out what is going on with it.... |
|
Success! The 0x12 encryption algorithm patially encrypts the media packets. Binary data can now be encryted if the |
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.
Seems that something is up with login on latest firmware. This PR will try to address that (also fix some other bugs)
Now that all discovery happens with a single handller special care needs to be done to handle the case where multiple threads subscribe to all messages