Openssl decrypt not producing plain text, encoding problem or corrupted file?

[AsaBarthMaron]

I have previously used the openssl method successfully on a different wallet, and got the WIF key (not mnemonic phrase). But now I am having another issue with a different wallet. When I try to decrypt with the correct password it produces something other than plain text or even hex. It is clearly binary, or protobuf, or some other format.

For example, if I try to open the output file in a text editor the beginning looks something like:

V∑4ìW�OŸi(w�h¯ÅµíA\�

�+‡-鱇C¥�k7πaÿ±⁄dÄ�•F�“�ˆ °!‘±4ÇÒ\8#`.... (truncated)

Is it possible that this file is corrupted? I feel like I am very close but just can't figure out the encoding.

[AsaBarthMaron]

It is similar to other android app backups, ~240 bytes for the encrypted, ~160 for the decrypted. Though a different backup is ~350 bytes encrypted, ~240 bytes decrypted.

[maximegalon5]

@AsaBarthMaron I am facing a similar issue and it's not clear to me if I'm implementing the openssl method correctly or not. I have an old Android backup from early 2014. ~240 bytes encrypted and ~160 decrypted. When I try to restore the backup using the latest Android App, I get an error "Message missing required fields: network_identifier". I'm considering looking for an old APK but haven't been able to find one from 2014 as yet. If you find a solution please let me know. I'll do so too, if I can recover the backup. Cheers.

[maximegalon5]

@AsaBarthMaron I am facing a similar issue and it's not clear to me if I'm implementing the openssl method correctly or not. I have an old Android backup from early 2014. ~240 bytes encrypted and ~160 decrypted. When I try to restore the backup using the latest Android App, I get an error "Message missing required fields: network_identifier". I'm considering looking for an old APK but haven't been able to find one from 2014 as yet. If you find a solution please let me know. I'll do so too, if I can recover the backup. Cheers.

maybe your backup corrupted. you need decrypt the backup with openssl. if you can't make it, contact us.

Perhaps, but when I look at the Base64 rawToChar I see "Salted_***..." so I'm inclined to think it's either a password issue or an issue with the version of Openssl I'm using or a mismatch with the default hashing algorithm used in the old application. Will keep plugging away :)