Timeline for What is responsible for file permissions in a linux system?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2018 at 18:55 | comment | added | Silv | @神秘德里克, OK, I get the point. In case of computer systems I just tend to be more specific than in other areas. | |
| Dec 7, 2018 at 8:01 | comment | added | 炸鱼薯条德里克 | Who decide the temprature of your room? The manfacturer of AC, AC or You? | |
| Oct 17, 2018 at 18:44 | vote | accept | Silv | ||
| Oct 16, 2018 at 16:59 | comment | added | Silv | You mean that the actual permissions values are decided by administrators, and the filesystem just stores ACLs (as well as traditional Unix permissions)? | |
| Oct 16, 2018 at 15:25 | comment | added | 炸鱼薯条德里克 | Decide the permission of a file, and should the system care about extended ACL. | |
| Oct 16, 2018 at 12:33 | comment | added | Silv | @神秘德里克, thanks. I am aware that names in the field of operating systems are a bit messy (it annoys me sometimes). Thanks for clarification of them, it helps me more understand the subject. But… I do not understand what do you mean "OS developer or Admin user decide it". They decide about what: about how/whether the permissions are stored in the filesystem, or how they are used in the operating system, or? | |
| Oct 16, 2018 at 6:43 | answer | added | dirkt | timeline score: 2 | |
| Oct 16, 2018 at 4:30 | comment | added | 炸鱼薯条德里克 | All the Permissions are stored in the filesystem, OS developer or Admin user decide it. ACL controls who can read/write/execute the file, but it's stored in a weird way, two parts separately stored in filesystem structure. First part is called traditional Unix permission, second is called ACL (not "extended-part-of-ACL", just ACL, very strange). You should now notice what's weird about how we call things. | |
| Oct 16, 2018 at 0:48 | comment | added | Silv | And I do not know, but SELinux (so, its permissions) seems to me to be a different, separate concept to file permissions, and at least for now I would rather not mix it with my question. | |
| Oct 16, 2018 at 0:44 | comment | added | Silv | @AaronD.Marasco, thanks. That is possible that I am combining these things… I am trying to understand file permissions as broadly as it can be; maybe it is not the best way. So, as these things are different, may it be that the "traditional Unix permissions" are defined by e.g. the filesystem, and the ACLs are defined e.g. by the OS? | |
| Oct 16, 2018 at 0:33 | comment | added | Aaron D. Marasco | (Then on top of all that there's also SELinux permissions as well...) | |
| Oct 16, 2018 at 0:32 | comment | added | Aaron D. Marasco | You are combining two different things. "Traditional Unix permissions" are only a simple bitmask field, stored in the file's metadata along with modification timestamps, etc. ACLs are newer and allow much finer control, including layered permissions, e.g. this group can write but not that one guy in the group. | |
| Oct 15, 2018 at 23:39 | history | asked | Silv | CC BY-SA 4.0 |