Re:How I Hacked Telegram’s “Encryption”
by itistoday2 on Monday February 23, 2015 @01:25PM
(#9095902)
Yeah, the memory thing didn't impress me. More concerning though is that apparently messages are stored in plain text on disk in that cache4.db file. It's not clear to me whether they are deleted when the app quits or what.
Yeah, I'm feeling like the quotes should be around "Hacked", and not "Encryption"
The files under `/data/data/[pkgname]` are only readable by the corresponding application. Encrypting them wouldn't add any security as the key for that cache would also be stored on the device.
Re:How I Hacked Telegram’s “Encryption”
by itistoday2 on Monday February 23, 2015 @01:42PM
(#9096054)
> Encrypting them wouldn't add any security as the key for that cache would also be stored on the device.
That's why you use a user-derived key (i.e. based on the pin or w/e).
I don't understand how this is a valid exploit/vulnerability? How would any device, Android or not, render the actual picture of the message on the GPU without having the unencrypted string in memory? It's not possible. If you have local memory/code execution, you will ALWAYS have access to the messages any client application is rendering/using.