3 ms·
This seems to me to be a rather daft policy for determining which files are sensitive and which aren't. To be sure, I don't know what the right way would be-- I
by cgranade 16y ago
This seems to me to be a rather daft policy for determining which files are sensitive and which aren't. To be sure, I don't know what the right way would be-- I'm guessing something based on paths would work a lot better-- but this solution clearly has serious problems.
- malkia 16y agoMaybe they could've checked only for files coming out of C:\Windows, and some from the "Common Files" of "Program Files" or "Program files (x86)" I came to appreciate Linux/Mac OSX/FreeBSD style of putting everything in place - /bin/ /usr/sbin/, etc. With Windows it's just folders everywhere :) For example the German version of Windows might have C:\Program Files named differently
- cgranade 16y agoThere is a notion of special directories under Windows, so you can request the Program Files directory without knowing even what drive it would be on. I do realize that a path-based whitelisting approach would introduce unwanted limitations, but considering the cost of false positives, it may be warranted to accept such limitations.