Kid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 2 years agoSignal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square15fedilinkarrow-up136cross-posted to: privacy@lemmy.worldfoss@beehaw.orgprivacyguidesprivacy@lemmy.ca
arrow-up136external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comKid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 2 years agomessage-square15fedilinkcross-posted to: privacy@lemmy.worldfoss@beehaw.orgprivacyguidesprivacy@lemmy.ca
minus-squaresun_is_ra@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 years agothere is SELinux which give more fine tuned permissions for each app but it was too complicated for me
minus-squareSethayy@sh.itjust.workslinkfedilinkEnglisharrow-up2·2 years agoAnd if you’re using SELinux as a kwallet/keyring replacement, you’re using it wrong (but again security in layers doesn’t stop you from using both)
there is SELinux which give more fine tuned permissions for each app but it was too complicated for me
And if you’re using SELinux as a kwallet/keyring replacement, you’re using it wrong (but again security in layers doesn’t stop you from using both)