Nemeski@lemm.ee to privacy@lemmy.ca · 7 个月前Signal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square16fedilinkarrow-up182arrow-down119cross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.one
arrow-up163arrow-down1external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comNemeski@lemm.ee to privacy@lemmy.ca · 7 个月前message-square16fedilinkcross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.one
minus-squarem-p{3}@lemmy.calinkfedilinkarrow-up11·7 个月前Storing the encryption keys in the Credentials Manager (Windows) or the Keychain (macOS, Linux) would be a better choice than a plaintext file. And using Bitlocker / VeraCrypt / Filevault / LUKS will at least protect the data at rest. But as you said, it’s game over if the machine is compromised.
Storing the encryption keys in the Credentials Manager (Windows) or the Keychain (macOS, Linux) would be a better choice than a plaintext file.
And using Bitlocker / VeraCrypt / Filevault / LUKS will at least protect the data at rest.
But as you said, it’s game over if the machine is compromised.