Re: Encryption backdoor takes it up the ...
"that wouldn't help with the apps on the phones"
Someone like me would invent a new "not back door" encryption 'app' that would a) act like a file system, storing your data encrypted within it as if it were an SD card or other removable storage; b) use a very strong encryption method that's well known and well published and has NO! BACK! DOOR!!! [with a HUGE key that's hashed from an arbitrarily long pass phrase plus a salt that's stored as part of the device itself]
So to decrypt the file you wouldn't just be able to take the SD card out and put it into another device; you'd have to at LEAST analyze the device and know what "salt" data needs to be used when generating the hash from the password. That's one possibility, anyway [others also exist].
This way, the app ITSELF does the encrypting, and it deliberately has NO back door. Although, I suppose storing the SALT within a 'back door-able' encrypted file isn't that bad. Sure, yeah, why not! Throw 'em that bone!
That way, ONLY those who used this (illegal?) app would have STRONG encryption, and you KNOW that anybody getting ahold of that APK would be able to install/run it, and even if you PUBLISH THE SOURCE, it wouldn't matter much, would it? [then anybody with an SDK could build the thing and install it as 'a developer' or on a jailbroken phone]
And THIS just proves how POINTLESS the argument is to have a "not a backdoor, seriously, not!" encryption method. With a back door. Shhhh...