←back to thread

Against /Tmp

(dotat.at)
140 points todsacerdoti | 1 comments | | HN request time: 0s | source
Show context
gnramires ◴[] No.41915682[source]
I really think there are quite a few reforms and new ideas that could help Unixes. Also it's not only about introducing features/new ways, but also the right culture and instruction around the new ways.

For example, the Android(/iOS?) permission based model at kernel level where apps (that could be processes in general?) can only access some private storage (which presumably has its own isolated tmp/ directory) really should be default, and permissions should be opt-in (of course, there should be a 'legacy permission' that makes things work as before).

(I believe most of permission functionality is technically possible through SELinux (??), or you could use containers, but is not easy to use or default)

I think containers arose partially to provide some of this isolation? But they have their own overhead and redundancy issues.

---

It seems some of this work is being done in SELinux project? Is it going to be enough? (and easy enough to use by default?)

https://wiki.archlinux.org/title/SELinux

I think a simple permission model might have been more elegant than the SELinux model ?

replies(1): >>41916529 #
1. anthk ◴[] No.41916529[source]
Pledge/unveil it's intristic, per software, under OpenBSD.