Am I tripping or if you upgrade Signal Desktop, it saves all your messages in plain text (messages.json) + attachments locally so you can re-import them in the newer version? #fail #wtf
-
-
Replying to @msuiche
There is no magical pixie dust encryption algorithm that will protect your messages in such a way that whatever new version of Signal can access them but no other app or user can (on a desktop). If you have local access it's game over.
5 replies 1 retweet 12 likes -
How about a non-magical average good encryption scheme where messages stores are encrypted using a password as salt? I don't know why you need to be condescending or exasperated about something as basic as encryption at rest.
1 reply 0 retweets 3 likes -
Replying to @dreamandghost @msuiche
What's the point? So you save the messages encrypted, import them, and then what? They're going to be decrypted to be useful, with credentials that any other app can hijack out of the running Signal instance even if they're encrypted "at rest".
6 replies 0 retweets 3 likes -
If you encrypt at rest with a password based key (using KDF) that you don't store anywhere, and decrypt only chunks of the data at rest to store in memory, then you are limiting the attack surface. Also, this helps against device theft where they don't conrol your running app
1 reply 0 retweets 1 like -
Unless you want to input your password for every single message you view, the key has to be in memory while you use the app, at which point any other process can grab it.
2 replies 0 retweets 3 likes -
You're solving these problems with the wrong, insufficient solution. This isn't Signal's job. Use sandboxing or user isolation to protect apps from each other. Use FDE and lock screens to protect against device theft.
2 replies 1 retweet 5 likes -
Yeah, you are right. Windows should also store credentials in json plain text on the disk to make
@gentilkiwi job easier for mimikatz. And users should just use Bitlocker as a security boundary against mimikatz.1 reply 0 retweets 3 likes
Why are you conflating credentials and data? You know full well we store passwords *hashed* (not encrypted) for good reasons. That provides a useful security bound since the plaintext password only has to be in memory when it is typed and checked.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.