Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I just bought Titanium Backup and set up a scheduled encrypted backup of user+system apps and data, followed by Dropbox sync. Assuming I remember the passphrase, is all the data required for restoration backed up? Or do I have to manually backup the private key and encrypted symmetric key?

share|improve this question
add comment

2 Answers

You only need to remember the passphrase. I've done this before.

If you're worried, you could always create a nandroid backup of your entire system, then wipe and install a custom rom. Install TB, and try to restore an app with just a passphrase. If it needs something you lack, then you have your answer and can go back to recovery and restore the nandroid. But as I said, I have done this process already and know that the password is all that is needed.

share|improve this answer
add comment

The FAQ of Titanium Backup about crypthography states that you just need the passphrase to recover any backup. That must mean that the private key file is stored along with all of your backups, because it could never work in any other ways. The big problem with that FAQ is that it should states this explicitly IMHO so to make things clearer for us users.

I took a peek at the first bytes of some backupped file (I am talking about the application data here, because Titanium Backup does not backup apks period), guess what I saw?

I found the very same ASCII sequence in the first lines of the backup files: those files are named something.gz but they are actually not gzip files (because of the key that has been put in front of them. Gzip files begin with hex codes 1F 8B 08. Those files do not).

If you run Linux and want to check it out, download two of your backups on the PC and try this command, that shows the first four lines of the file:

$ head -n 4 cgeo.geocaching-20130919-000250.tar.gz

My output is:

TB_ARMOR_V1
0w5AkcCA9rGtSy3Ecrag19p/FYQ=
BNpyGZq/PQYmpDXkXwji2lQGIQY=
MIGfMA0GCSqGSIb3DQEBAQUAA5GNADCBiQKBgQDWLUH3i295TA9XwPgbzwXEk/0eqowW2xcoxbOQo7NYeqGvctC7dNM33CEh+az25Wj2iTo+kzdIpwM7Y6o5vjW+D/yBCv9nDV1+HLNyut3GDQon84yR6BlgbQJT5QoIra5f6FN+wtqF5/ifW88nzuia2fUOv/IqRVQhHxIY7LPkMQIDAQAB

Quite odd for a binary file, isn't it? By the way that must be, yes, my TB private key enciphered with my passphrase. I don't give a thing about sharing it because you would need my backup files and my passphrase as well, to get anything useful out of.

Now, if you run run the same command on a different backup file:

$ head -n 4 com.amazon.kindle-20130919-000004.tar.gz

Guess what? You'll get the same s*it!

TB_ARMOR_V1
0w5AkcCA9rGtSy3Ecrag19p/FYQ=
BNpyGZq/PQYmpDXkXwji2lQGIQY=
MIGfMA0GCSqGSIb3DQEBAQUAA5GNADCBiQKBgQDWLUH3i295TA9XwPgbzwXEk/0eqowW2xcoxbOQo7NYeqGvctC7dNM33CEh+az25Wj2iTo+kzdIpwM7Y6o5vjW+D/yBCv9nDV1+HLNyut3GDQon84yR6BlgbQJT5QoIra5f6FN+wtqF5/ifW88nzuia2fUOv/IqRVQhHxIY7LPkMQIDAQAB

This simply could not be a coincidence. :) From a certain point onward everything in backup files finally becomes binary. This behavior makes a lot of sense because that would mean that we can only share the backup files and forget about everything - with the passphrase, we can recover our backups, period.

Still, I really think that the developer should document a procedure about how to recover our own legitimate data (we know the passphrase, so it's us!) from any computer with a decent crypto tools set (read: OpenSSL).

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.