KidMtoCybersecurity@sh.itjust.worksEnglish·3 months agocross-posted to: privacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.oneSignal under fire for storing encryption keys in plaintext(stackdiary.com)external-linkarrow-up135arrow-down118message-square15fedilink
arrow-up117arrow-down1external-linkSignal under fire for storing encryption keys in plaintext(stackdiary.com)KidMtoCybersecurity@sh.itjust.worksEnglish·3 months agocross-posted to: privacy@lemmy.worldprivacy@lemmy.mltechnology@lemmy.worldfoss@beehaw.orgprivacyguides@lemmy.onemessage-square15fedilink
minus-squaresun_is_raEnglisharrow-up1arrow-down0·3 months agolinkfedilinkthere is SELinux which give more fine tuned permissions for each app but it was too complicated for me
minus-squareSethayyEnglisharrow-up2arrow-down0·3 months agolinkfedilinkAnd 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)