Nemeski to Privacy [email protected]English • 2 months agoSignal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square46fedilinkarrow-up1213arrow-down12cross-posted to: cybersecurity[email protected][email protected][email protected][email protected]
arrow-up1211arrow-down1external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comNemeski to Privacy [email protected]English • 2 months agomessage-square46fedilinkcross-posted to: cybersecurity[email protected][email protected][email protected][email protected]
minus-square@[email protected]linkfedilinkEnglish43•2 months agoIt is a super important detail, but it’s still unforgivable for an app that expects privacy to be part of its brand identity.
minus-square@[email protected]linkfedilinkEnglish3•2 months agoThis is a big difference between privacy and security.
minus-square@[email protected]linkfedilinkEnglish2•2 months agoAgreed But you can’t have privacy without security, and any privacy brand must have security in their bones.
minus-square@[email protected]linkfedilinkEnglish7•2 months agoYou can’t encrypt anything without a key. This is the key. If it wasn’t in plaintext then it would be encrypted. Then you’d need a key for that. Where do you put it? Phone OSs have mechanisms to solve this. Desktop ones do not.
It is a super important detail, but it’s still unforgivable for an app that expects privacy to be part of its brand identity.
yeah absolutely agreed
This is a big difference between privacy and security.
Agreed
But you can’t have privacy without security, and any privacy brand must have security in their bones.
You can’t encrypt anything without a key. This is the key. If it wasn’t in plaintext then it would be encrypted. Then you’d need a key for that. Where do you put it?
Phone OSs have mechanisms to solve this. Desktop ones do not.