DCL via memory and storage

Sagebath

Looking for an explanation of DCL via memory setting. DCL makes the app more vulnerable, so doesn't it make sense to set this to restricted for everything unless / until the app fails?

0xC0DED0D0

Yup, that's what I did. Won't break anything permanently, just crash the app attempting DCL.

If I believe the DCL to be legitimate (which it most likely always is), it's very simple to add an exception straight from the notification.

Bear in mind that you do run a slight risk of losing work, at the moment of forced crash, depending on the app and the timing of DCL within the app's logic. Hence why the restriction isn't activated by default.

You decide if this is an acceptable risk in your usage case.

Sagebath

IronFox won't work with dcl restricted. Does this mean it's not as safe/secure as other browsers that do work with dcl restrictions? I know this is an oversimplification, but IDK how else to start the conversation.

Sagebath

Sagebath
Anyone understand DCL and what it means for privacy/security?

God

Sagebath if you're curious here are sources addressing ironfox's/firefox's limitations security wise.
https://ironfoxoss.org/docs/limitations/

https://grapheneos.org/features#vanadium

I would definitely look over them, or investigate further.

de0u

Sagebath Some exploits rely on injecting code and running it, so disallowing that improves resistance to those exploits. Unfortunately, some apps load code while running, so those apps won't run if code loading is disabled. When possible, using a different app is arguably safer.