@ForgottenFlux@lemmy.world to Privacy@lemmy.mlEnglish • 2 months agoSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.comexternal-linkmessage-square258fedilinkarrow-up1503arrow-down130cross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldtechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.oneprivacy@lemmy.ca
arrow-up1473arrow-down1external-linkSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.com@ForgottenFlux@lemmy.world to Privacy@lemmy.mlEnglish • 2 months agomessage-square258fedilinkcross-posted to: cybersecurity@sh.itjust.worksprivacy@lemmy.worldtechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.oneprivacy@lemmy.ca
minus-square@fuzzzerd@programming.devlinkfedilinkEnglish4•2 months agoI was just nodding along, reading your post thinking, yup, agreed. Until I saw there was a PR to fix it that signal ignored, that seems odd and there must be some mitigating circumstances on why they haven’t merged it. Otherwise that’s just inexcusable.
minus-square𝙲𝚑𝚊𝚒𝚛𝚖𝚊𝚗 𝙼𝚎𝚘𝚠linkfedilink7•2 months agoThe PR had some issues regarding files that were pushed that shouldn’t have been, adding refactors that should have been in separate PRs, etc… Though the main reason is that Signal doesn’t consider this issue a part of their threat model.
I was just nodding along, reading your post thinking, yup, agreed. Until I saw there was a PR to fix it that signal ignored, that seems odd and there must be some mitigating circumstances on why they haven’t merged it.
Otherwise that’s just inexcusable.
The PR had some issues regarding files that were pushed that shouldn’t have been, adding refactors that should have been in separate PRs, etc…
Though the main reason is that Signal doesn’t consider this issue a part of their threat model.