just brew it! wrote:
How about just letting \Windows\Temp inherit its permissions from \Windows so its size isn't hidden by default? With all the other behavioral differences between different Windows flavors, that's pretty minor.
that Windows\Temp has higher permissions because per user data can be comingled inside that directory. Even if I'm mistaken about the potential leakage of user data within that directory, system level services/daemons work out of the directory. A point made evident through this very bug and thread. Microsoft has apparently decided there's no good reason for users to even have read permissions (which includes directory listing info) to the user.
One could point to Linux and say, "Linux handles this without issue with /tmp."
Yeah, it does, but it also has a number of features Windows doesn't have and a file system ACL system that isn't as strict. The DAC (Discretionary Access Control) functionality of EXT4 is not the ballbuster that NTFS is. Linux also has the sticky bit and SUID or GUID to handle such delicate issues. Windows does not have these things.
At the heart of this problem is a difference in security paradigms. Accusing Windows of acting in bad faith for obeying it's security paradigm is like accusing Linux of bad faith for doing what you tell it to do.Remember when you told Linux to do this and it did?
And this is why we all love Unix - because when you break your system you know EXACTLY what a muppet you were!
You're not technically asking Windows to "stop lying to you," you're asking a DAC to stop lying to you. It's not lying, it's doing it's job, and in this case its job is to be purposefully opaque.
I'm sure there's some non-Microsoft dude from the 70's you can yell at for creating DAC's that are this strict. I suppose you can blame Dave Cutler for NTFS having a strict DAC. I'd also assume the filesystem DAC in VMS has the same "quirk."
I will say this about this particular bug. I believe the Windows Update service should have more logic built into it for sanity checks and disk cleanup. I also firmly believe that the built in Windows cleaning tool cleanmgr.exe should be dealing with this issue and according to feedback it's not. Failure of cleanmgr.exe to deal with this is facepalm worthy.
All of my written content here on TR does not represent or reflect the views of my employer or any reasonable human being. All content and actions are my own.