3 ms·
~/.local on the other hand will frequently include information that under a tighter permission system should not be accessed without approval. Things like my c
by shakna 7y ago
~/.local on the other hand will frequently include information that under a tighter permission system should not be accessed without approval.
Things like my complete shell history can be found there.
- dylan604 7y agoThe fact that you are worried about your shell history proves you are not one of the average users.
- shakna 7y agoAnd? How is that relevant to the permission system? The average person doesn't need to care whether a file is executable or not.
- comex 7y agoYep. But authorizing things on a file-by-file basis would be a terrible UX, while granting programs blanket access to all of ~/.local wouldn't be very secure, since lots of programs need something from there. It's the same situation as ~/Library for macOS-specific code. App Sandbox avoids this problem by giving each app its own virtualized home directory, so that data sharing between apps becomes opt-in instead of opt-out. It still exists... too bad nobody wants to adopt it.