> I do not see a "typical" user needing to access a path with say...
replyTypical users run software written by atypical users.
> some sort of OS-wide single-implementation
How do you propose handling migration? What if someone tries to expand an old archive file containing a now-forbidden path?
What I mean is that for “honest” software, built-in to the OS or otherwise, the programmer finds a situation where they take some user-supplied input and concatenate that into a path, and call something like OS.read(). If they want to prevent the user from causing havoc, they now find themselves dealing with path validation in their software instead of calling OS.safeOpen(), which would be a reduced subset of allowed chars?
replyIf the OS is working properly, the havoc should just result in "permission denied."
replyIf there's a path on the system that the user should not be able to read, that's the job of the OS to handle, not the individual applications.
How would you enforce a single implementation of path parsing?
reply