Support for devices using AES-GCM encryotion #64
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
New devices are using AES-GCM encryotion for communication More details about the problem in tomikaa87#52
Search command can find more than 1 device with different encryption types - add property encryption to each found device and try to bind with it. When connectiong to one particular device the encryption mode should be set globaly when the script is run with -e option
Change the check from bc property with 0 to version equal to 2 or later. Also in case of socket.timeout exception when bind request is sent try again with a bind request with 'GCM' encryption
lovery
force-pushed
the
feature/gcm-encryption-python
branch
from
904bb8b
to
e5c1065
Compare
|
Thank you for the patch! |
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.
New devices are using AES-GCM encryotion for communication More details about the problem in #52