@ForgottenFlux@lemmy.world to Privacy@lemmy.mlEnglish • 5 months agoSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.comexternal-linkmessage-square258fedilinkarrow-up1513arrow-down130cross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldtechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.oneprivacy@lemmy.ca
arrow-up1483arrow-down1external-linkSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.com@ForgottenFlux@lemmy.world to Privacy@lemmy.mlEnglish • 5 months agomessage-square258fedilinkcross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldtechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.oneprivacy@lemmy.ca
minus-squareMr. Satanlink11•5 months agoHowever, you can save encrypted ssh, gpg keys and save that encryption key in the OS keyring.
minus-square@uis@lemm.eelinkfedilink3•5 months agoYes, but you STILL need to enter password on every reboot.
minus-square@derpgon@programming.devlinkfedilink2•5 months agoIs it possible to seamlessly integrate, so when something requests those keys you’ll get a prompt?
minus-squareTodd Bonzalezlinkfedilink11•5 months agoWith SSH at least you can password protect the key itself so that you always get a prompt.
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