Andrew doesn’t know how file system permissions work. He complains that computers demand he keeps up, but these ACLs have been a thing since Windows XP (for consumers, much longer for older NT versions) so clearly the 14 years he had to catch up weren’t enough.
I’m not sure why he brought up moving to 64 bit (guess he came from XP, perhaps?), I don’t think thats relevant to anything here.
He doesn’t seem to know what an administrator account is (so his normal account probably is an administrator account) and rants something about “owners” as if that means anything to a computer.
He also concludes that this needs to be done for every file (it doesn’t) and then gets mad about that.
Fixing ACLs sucks, it takes forever and the UI isn’t very good for novices, but this guy’s anger seems to be misdirected towards his own misunderstandings about how Windows works and has worked for over a decade at the point he came to the forums.
None of this is because of “changes”, if anything his problem is exacerbated by the fact Windows still has the Win2000 permissions dialog on ACLs to this day.
Windows permissions can be tricky… I’ll give them that. A lot of the tools Microsoft provides are not very straightforward.
However, PowerShell and tools from Sysinternals suite, or open source tools as well, make it a lot easier.
Managing permissions on Linux, especially if doing the ACL thing, can be complicated too. I’ve really never ran into many permission issues myself. psexec has been helpful too when needing to access things as the SYSTEM user and not get those stupid prompts asking me to change permissions for protected folders.
Having used secured SELinux enterprise code, I’ve learned that Linux permissions can be even more complicated than Windows’ when multiple permission models suddenly overlap. There’s an endless supply of special bit flags, security contexts, and sandboxing features that all overlap.
I’ve run into very complicated Linux permission issues when combining SELinux (properly configured, not just neutered and standby) and system services in some specific configuration. Once you start applying the permission systems that Windows comes with by default in Linux, you get the same problems (or worse ones, as Linux has a multitude of permission systems stacked on top of each other).
On Windows, I recall one particularly messed up drive from another computer that not even NT_AURHORITY\SYSTEM was allowed to alter the ownership of. Luckily Linux happily stripped out all the permissions for me because Linux can plainly ignores ACL if you’re root and provide the right flags. Probably a terrible way to break ACLs in a managed environment, but this time it was a feature!
We tend to forget about it these days, but the Unix permissions model was criticized for decades for being overly simplistic. One user having absolute authority, with limited ways to delegate specific authority to other users, is not a good model for multi-user operating systems. At least not in environments with more than a few users.
A well-configured sudo or SELinux can overcome this, which is one reason we don’t bring it up much anymore. We also changed the whole model, where most people have individual PCs, and developers are often in their own little VM environment on a larger server.
I agree with the critics, the Unix permission model is too basic. I’ve run into this myself doing the very difficult operation of “reusing an ext4 USB drive on another computer” because all the files were suddenly owned by a user that didn’t even exist on my laptop.
NTFS fixed this issue by having the OS generate user IDs across systems rather than reusing the same IDs and making the administrators match everything up. I don’t think selinux can fix that, though.
I welcome the extensions bringing Linux’ permission model to the 21st century, but the way they’ve all been implemented independently does cause some weird edge cases that clearly nobody has tested.
Andrew doesn’t know how file system permissions work. He complains that computers demand he keeps up, but these ACLs have been a thing since Windows XP (for consumers, much longer for older NT versions) so clearly the 14 years he had to catch up weren’t enough.
I’m not sure why he brought up moving to 64 bit (guess he came from XP, perhaps?), I don’t think thats relevant to anything here.
He doesn’t seem to know what an administrator account is (so his normal account probably is an administrator account) and rants something about “owners” as if that means anything to a computer.
He also concludes that this needs to be done for every file (it doesn’t) and then gets mad about that.
Fixing ACLs sucks, it takes forever and the UI isn’t very good for novices, but this guy’s anger seems to be misdirected towards his own misunderstandings about how Windows works and has worked for over a decade at the point he came to the forums.
None of this is because of “changes”, if anything his problem is exacerbated by the fact Windows still has the Win2000 permissions dialog on ACLs to this day.
Windows permissions can be tricky… I’ll give them that. A lot of the tools Microsoft provides are not very straightforward.
However, PowerShell and tools from Sysinternals suite, or open source tools as well, make it a lot easier.
Managing permissions on Linux, especially if doing the ACL thing, can be complicated too. I’ve really never ran into many permission issues myself. psexec has been helpful too when needing to access things as the SYSTEM user and not get those stupid prompts asking me to change permissions for protected folders.
Having used secured SELinux enterprise code, I’ve learned that Linux permissions can be even more complicated than Windows’ when multiple permission models suddenly overlap. There’s an endless supply of special bit flags, security contexts, and sandboxing features that all overlap.
I’ve run into very complicated Linux permission issues when combining SELinux (properly configured, not just neutered and standby) and system services in some specific configuration. Once you start applying the permission systems that Windows comes with by default in Linux, you get the same problems (or worse ones, as Linux has a multitude of permission systems stacked on top of each other).
On Windows, I recall one particularly messed up drive from another computer that not even NT_AURHORITY\SYSTEM was allowed to alter the ownership of. Luckily Linux happily stripped out all the permissions for me because Linux can plainly ignores ACL if you’re root and provide the right flags. Probably a terrible way to break ACLs in a managed environment, but this time it was a feature!
We tend to forget about it these days, but the Unix permissions model was criticized for decades for being overly simplistic. One user having absolute authority, with limited ways to delegate specific authority to other users, is not a good model for multi-user operating systems. At least not in environments with more than a few users.
A well-configured sudo or SELinux can overcome this, which is one reason we don’t bring it up much anymore. We also changed the whole model, where most people have individual PCs, and developers are often in their own little VM environment on a larger server.
I agree with the critics, the Unix permission model is too basic. I’ve run into this myself doing the very difficult operation of “reusing an ext4 USB drive on another computer” because all the files were suddenly owned by a user that didn’t even exist on my laptop.
NTFS fixed this issue by having the OS generate user IDs across systems rather than reusing the same IDs and making the administrators match everything up. I don’t think selinux can fix that, though.
I welcome the extensions bringing Linux’ permission model to the 21st century, but the way they’ve all been implemented independently does cause some weird edge cases that clearly nobody has tested.
Omg, it’s an inside-joke at our company now.
Anytime something happens on a server that’s been running great for years, like a hard drive going bad or the time one literally caught on fire…
98% of the time it is selinux that is the reason it is doing weird things after the main fix because selinux changed a setting on the reboot.
“Have you checked selinux?” is the go to question whenever anything breaks now, even if it’s not a computer.