-
Notifications
You must be signed in to change notification settings - Fork 6
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
Abus Secvest encryption doesn't work #6
Comments
Hi Patrick |
Thx, for your answer. I have included an output of "pad", "padlen" and "result" in the script. This is the output: "- -" are separators. The value "pad" is empty. Is it right so? Sry, I haven't worked with buffers yet and I'm not familiar with them. |
Hi |
Hey, That's exactly it, I've never worked with buffers before, that's why I turned to you. But I can tell you how it has to work. The pad must always be a multiple of 16. That works!
How do I get it to generate binary data?
The Buffer.alloc should generate the data.
But in the console.log the pad is empty... I added the code: and the result is:
The buffer should have a size of 10. Thats right. Best regards, Patrick |
In my opinion, a random of characters that corresponds to the length of padlen would first have to be generated. Then this part must be converted to byte (decimal or hex). The characters “[ ] |” cannot be used. How do you implement this in code? |
Hi |
Hey, the iobroker-adapter has the same issue. Your code supports the unencryption messages :) |
Hey,
have you already taken a look at the code?
I tried to do a little research. But I can't get any further with the "pad" because I don't know how to create binary arrays.
Maybe together we can get the script running.
Greetings
Patrick
… Am 09.03.2024 um 13:58 schrieb Massimo Saccani ***@***.***>:
Hi
The node is based to iobroker sia implementation
Monday l’ll take a look
—
Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BE5MVKHJRA2QQFFCZFP6NELYXMBOXAVCNFSM6AAAAABEMTIQVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHA2TANBYGU>.
You are receiving this because you authored the thread.
|
Hi Patrick |
Hello :)
with my Abus Secvest, i have a problem with your code.
Messages without AES-encryption work fine, but with the encryption, your adapter received the encrypted message and decrypts this. Everything is fine up to this point.
But, the acknowledge is not understood by the system and the Secvest issues a reporting fault.
No matter whether 128, 192, 256 aes-encryption.
Do you have help for me?
Greetings
Patrick
The text was updated successfully, but these errors were encountered: