in reply to Re^2: To taint or not to taint?
in thread To taint or not to taint?

The point of taint checking is to make the programmer decide what is risky. Obviously the config file that is that protected is safe, and so blindly untainting it is reasonable. That is the cost of the double-check that the checks I care about on my users really are being done as I think they are.

Replies are listed 'Best First'.
Re^4: To taint or not to taint?
by clinton (Priest) on Mar 19, 2009 at 15:44 UTC

    Makes sense.

    Which has made me think, I could change my config loader to automatically untaint all the data it loads from a file if the file is writable only by the current user, no?

[reply]
      That would be a perfectly reasonable change for any non-suid script. Because any damage that can be done by changing that file can be done more easily directly without using your script.
[reply]

In Section Meditations