3 ms·
this is all greet but I shouldn't have to trust app makers. the os shouldn't allow an app to read another app's data without permission. the os also shouldn't a
by tokyodude 8y ago
this is all greet but I shouldn't have to trust app makers. the os shouldn't allow an app to read another app's data without permission. the os also shouldn't allow an app to view what other apps are running
Epic might be doing the right thing today. Will they tomorrow? Is every library they use trustworth forever?
- ourmandave 8y ago"I am altering the deal. Pray I don't alter it any further." ~ Darth Vader You can read the changes to the ToS at www.palpatine2020.com/toremotetomakeaneffectdemonstration
- chris_mc 8y agoI'm starting to think something like flatpak or snap is necessary, but in a more sandboxed way, to enforce on the user level that certain apps won't have access to certain files. I would like to see options to fully sandbox an app (has it's own separate permissions for certain documents) or not sandbox it at all (for things we trust implicitly that need that access).
- danShumway 8y agoflatpak permissions + Wayland are (imo) some of the best things happening on Linux right now. You could always kind of do the same stuff with containers and custom wrappers around each program, but it's really cumbersome. I want this to be the normal. Right now, it's basically a free for all -- record the screen, send network requests, fingerprint hardware, scan for files, examine other processes. The default, out-of-the-box security settings for most distributions are unacceptable. I'm really excited to see that sandboxing on native is starting to move in the same direction as the web; I'm hoping that within the next year or two we start to see dramatic improvement here.