Comment on Signal under fire for storing encryption keys in plaintext on desktop app
ForgottenFlux@lemmy.world 3 months ago
Researchers were able to clone a user’s entire Signal session by copying the local storage directory, allowing them to access the chat history on a separate device
This has actually been useful for me in the past when reinstalling my OS lmao. In an ideal world we could reverify by entering a code from our phones to unlock the desktop local storage after moving it. My biggest wish for Signal is more seamless message history movement across devices and ecosystems.
My biggest issue with Signal is it being so mobile-oriented. Mobile use seems to be encouraged, and even to register you are directly told to go to the mobile app (and if you register in a VM, you’re then stuck using it because it wants you to scan a QR code which is so easy to do in a VM!) No thanks, I don’t trust my mobile - they’re much harder to make private and “yours” than a desktop. Was it that hard to just add a field for entering the verification code in the desktop client? Sure, I did end up using signal-cli, but it is not mentioned anywhere officially. Point is about how the Signal itself tries to push you onto mobile.
I don’t trust my mobile - they’re much harder to make private and “yours” than a desktop.
Still mobile phones are designed with much more security in mind than desktop environments, and basically everybody has a device.
Security is not everything though, you need to balance it with privacy and independence as well. Which are, indeed, harder on Android.
Not having backups here on iOS stresses me out. I like using iOS beta updates, but knowing I’m one bad beta from having to restore my phone (where every other little thing except Signal is backed up and waiting) and lose my conversation history forever really bugs me.
asdfasdfasdf@lemmy.world 3 months ago
I hate hearing shit like this. What are they thinking?
MeanEYE@lemmy.world 3 months ago
They are thinking “your computer, your problem”.