bepaald
commented
4 months ago Hi! Thanks for your report.
This looks very strange to me. First of all, I see two unrelated problems in the output you posted:
[Warning]: Foreign key constraint violated. -------------------------------------- | table | parent | fkid | -------------------------------------- | msl_recipient | msl_payload | 0 | | msl_message | msl_payload | 0 | --------------------------------------
This is a problem in the Android backup you are opening, and should not naturally occur. Has anything been done to this backup? As it is, this backup will probably not restore on Signal (though this constraint violation is easily fixed).
Then the stranger one:
[Error]: BAD MAC! (pagenumber: 262145) MAC in file: (hex:) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Calculated : (hex:) 72 84 59 cf df c8 32 a8 52 bf bd 13 b8 0c e2 43 14 cc 9a 23 2f 73 8c 3b 9d 98 a1 61 57 24 c6 92 f6 f4 06 fe 88 51 b2 ce 09 e5 72 a3 85 e0 49 1b 5f 94 6b 4b 12 fd 95 df f6 1e c1 1d ef 7b 5a 52 [Error]: Failed to open Signal Desktop sqlite database
So, in the Desktop database (which is a sqlcipher database), each page is encrypted and then a checksum (SHA-512 hash) of this encrypted data is appended to the page. This checksum is the MAC. A bad MAC would normally indicate corrupted (encrypted) data, so it wouldn't have anything to do with corrupted messages (it hasn't gotten to those at this point yet).
The MAC read from file being all 0x00's is also an indication that the file might be corrupt.
However, the fact that you have this on two Desktop databases is curious. I'm assuming these are separate instances (not actual copies)? And the error is the same (including the exact pagenumber and calculated MAC)? Could you tell me the size of the database? It's located at ~/.config/Signal/sql/db.sqlite by default. I find the pagenumber at which it fails almost too special to be a coincidence: it is after 262144 pages, each 4096 bytes, which is 1073741824 bytes (exactly 1GiB), which I think is absolutely huge for a sql database. I almost think the program is reading past the end of the file (which could also explain the all 0x00's MAC), but don't see why it would do that.
Do these databases still work with Signal Desktop itself? It doesn't show any errors and messages can be sent and received normally? Since the database is a normal sqlcipher database, you could also consider — if you feel up to it — to just open it with another program (as long as the sqlcipher extention is installed). If you want to try this, the key is at ~/.config/Signal/config.json, I think there are a couple of how-to's available on the internet.
Currently, I must admit, I do not know what is going on, but I'll give it some thought. I hope some of the answers to my questions will also give me a hint.
Thanks again!
ImJustToNy
At first, thank you for this awesome application and all the work you've put into it :1st_place_medal: I have a problem, when trying to merge my desktop backup with android backup:
I tried debugging it, however, I have little to no clue why it might be this way. Perhaps corrupted message? Interestingly enough, same thing happened when doing the same thing on my other computer, also running same signal version, so I doubt that it is a problem with this particular DB. Any help appreciated.
Versions: