Nemeski ( neme@lemm.ee ) to Privacy Guides@lemmy.oneEnglish · 2 years agoSignal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square28linkfedilinkarrow-up1117cross-posted to: fossprivacy@lemmy.ca
arrow-up1117external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comNemeski ( neme@lemm.ee ) to Privacy Guides@lemmy.oneEnglish · 2 years agomessage-square28linkfedilinkcross-posted to: fossprivacy@lemmy.ca
minus-squarepearsaltchocolatebar ( pearsaltchocolatebar@discuss.online ) linkfedilinkEnglisharrow-up43·2 years agoBut… That’s how encryption keys are stored.
minus-squareboredsquirrel (he) ( boredsquirrel@slrpnk.net ) linkfedilinkEnglisharrow-up16·2 years agoopportunistic TPM integration would be nice. I.e. use the security chip of the device, if one is found. Otherwise use password. OR use a Nitrokey etc, which can act as a secure device to store these keys too. Take that, Windows. You dont need a builtin TPM if you can use a Nitrokey 3 with a secure element, externally.
But… That’s how encryption keys are stored.
opportunistic TPM integration would be nice.
I.e. use the security chip of the device, if one is found. Otherwise use password.
OR use a Nitrokey etc, which can act as a secure device to store these keys too.
Take that, Windows. You dont need a builtin TPM if you can use a Nitrokey 3 with a secure element, externally.