Solve problem CryptoStream transform error TypeError: Cannot read property 'length' of null with NodeJs v6.9.2 #17
Conversation
This file contains hidden or 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
added 2 commits
April 4, 2017 20:35
…sform error Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt"
|
I needed this patch on NodeJS v4.2.6 too. Thanks @arondn2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Patch to solve errors: "CryptoStream transform error TypeError: Cannot read property 'length' of null" and "CryptoStream transform error Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt" when a particle devices intent connect to local server running with a nodejs version v6.9.2.
I do not know if this change has any repercussion in other cases, but it works fine for me and maybe it do it for anyone else.