Kid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 2 months agoSignal under fire for storing encryption keys in plaintextstackdiary.comexternal-linkmessage-square15fedilinkarrow-up135arrow-down118cross-posted to: privacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.one
arrow-up117arrow-down1external-linkSignal under fire for storing encryption keys in plaintextstackdiary.comKid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 2 months agomessage-square15fedilinkcross-posted to: privacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.one
minus-squaresun_is_ra@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 months 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 months 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)