Nemeski to Privacy Guides@lemmy.oneEnglish • 6 months agoSignal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square49fedilinkarrow-up1214arrow-down10cross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacy@lemmy.ca
arrow-up1214arrow-down1external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comNemeski to Privacy Guides@lemmy.oneEnglish • 6 months agomessage-square49fedilinkcross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacy@lemmy.ca
minus-square@Tramort@programming.devlinkfedilinkEnglish3•6 months agoAgreed But you can’t have privacy without security, and any privacy brand must have security in their bones.
minus-square@claudiop@lemmy.worldlinkfedilinkEnglish7•6 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.
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.