@[email protected] to [email protected]English • 2 months agoSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.comexternal-linkmessage-square258fedilinkarrow-up1505arrow-down130cross-posted to: cybersecurity[email protected][email protected][email protected][email protected]
arrow-up1475arrow-down1external-linkSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.com@[email protected] to [email protected]English • 2 months agomessage-square258fedilinkcross-posted to: cybersecurity[email protected][email protected][email protected][email protected]
minus-squareMubelotixlinkfedilink61•2 months agoSure, I was aware. You have the same problem with ssh keys, gpg keys and many other things
minus-squareMr. Satanlinkfedilink11•2 months agoHowever, you can save encrypted ssh, gpg keys and save that encryption key in the OS keyring.
minus-square@[email protected]linkfedilink3•2 months agoYes, but you STILL need to enter password on every reboot.
minus-square@[email protected]linkfedilink2•2 months agoIs it possible to seamlessly integrate, so when something requests those keys you’ll get a prompt?
minus-squareTodd Bonzalezlinkfedilink10•2 months agoWith SSH at least you can password protect the key itself so that you always get a prompt.
Sure, I was aware. You have the same problem with ssh keys, gpg keys and many other things
However, you can save encrypted ssh, gpg keys and save that encryption key in the OS keyring.
Yes, but you STILL need to enter password on every reboot.
Is it possible to seamlessly integrate, so when something requests those keys you’ll get a prompt?
With SSH at least you can password protect the key itself so that you always get a prompt.
Nice, didn’t know, I’ll look into it