Nemeski@lemm.ee to Privacy Guides@lemmy.oneEnglish · 13 天前Signal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square46fedilinkarrow-up11arrow-down10cross-posted to: [email protected][email protected][email protected]
arrow-up11arrow-down1external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comNemeski@lemm.ee to Privacy Guides@lemmy.oneEnglish · 13 天前message-square46fedilinkcross-posted to: [email protected][email protected][email protected]
minus-squarekakito69@sh.itjust.workslinkfedilinkEnglisharrow-up0·13 天前Not storing it in plaintext would require setting up some kind of password, right?
minus-squareboredsquirrel@slrpnk.netlinkfedilinkEnglisharrow-up0·edit-213 天前Some way to encrypt the decryption key. This could also mean TPM + Pin. Or using a Nitrokey, externally, which stores the password to decrypt the decryption key. That is how user account unlocking (on GrapheneOS with Pixel phones) is done.
Not storing it in plaintext would require setting up some kind of password, right?
Some way to encrypt the decryption key.
This could also mean TPM + Pin. Or using a Nitrokey, externally, which stores the password to decrypt the decryption key.
That is how user account unlocking (on GrapheneOS with Pixel phones) is done.