-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
HMAC verification failed #36
Comments
Hello @necrophcodr , Unfortunately I could not verify your issue. Do you have any debug output ( Best |
I tried running it with the variable you requested as follows:
I'm not sure what database version it is. How would I figure this out? |
I'm sorry, the database version is shown after the first frame is decrypted. Does it always fail at the first frame? This could indicate that your password file is wrongly formatted. Only the first line is read of the password file. What happens if you add Edit: If you want to, you can test my pull request: https://github.com/mutlusun/signal-backup-decode |
Tried with the parameter and
I'll give the PR a try too. |
There's no difference with running it from your fork. Installed it using |
I'm sorry, I don't really know what's going on here. @pajowu do you have any idea? |
Don't forget the number one rule: the customer lies. I may be missing something somewhere or whatever that I just don't realize. I'm trying my best, but don't forget that I didn't write this, and have little to no knowledge about how it actually works, so if I'm doing something incorrectly, I probably wouldn't know. |
Also do note that I tried with an older password that no longer works, and it gave me the same output? The lengths are identical, but it appears that no matter what password I use, I get the same output. |
Turns out the key WAS incorrect. So I tried it with the correct key:
|
Freshly built from git.
I'm running into something similar, where over 9k frames get decoded before I run into HMAC verification:
with debug:
Their mac is 0 though -- is this the same issue or should I open a new one? This also happens with |
Thanks for your report. It would be cool to add a flag to recover from such errors (having only (at least) one bad frame). However, I have probably too less time to implement this at the moment. Regarding your current problem: A MAC with 0 seems strange to me. Maybe the backup is corrupt? Does this error also appear when creating a new backup and decoding this one? If you are depending on this backup and the files in it you can try the |
(I was already trying
and error still happened) Backup was freshly written, but I will try another one |
Meh, my error was NOT related to signal-backup-decode. I saved signal backups to the sd-card, which was formatted with exfat, which cut off the file at 4gb (but for some reason filesize after copying was still 6gb, I don't know) |
That's odd. exFAT supports files larger than 4GB just fine. |
Either way, the printed error should be another one with |
Same issue.
|
The latest version of signal-backup-decode doesn't appear to want to decrypt recent backups?
I've verified and re-created backups a couple of times now, and it always fails decrypting them again. However, noteworthy is that it isn't because the actual pass phrase is incorrect. I've tried with incorrect pass phrases, and it fails after a certain amount of frames, not after the first frame (which usually happens with incorrect pass phrases).
The text was updated successfully, but these errors were encountered: