I wish folks would use the taint mode they might already have. At some point taint checking bugs stopped being release blockers in core ruby & perl, but having worked through moving a couple of large codebases to surviving strict taint checking in prod, it's one of the most memorable systematic things we have to avoid (I think most?) of the bugs in the class that this is trying to solve.
Obviously, we want solutions that will remediate existing code unmodified, and I guess enabling taint mode isn't in that category.
I wonder what bugs taint checking wouldn't catch, that this would.
Obviously, we want solutions that will remediate existing code unmodified, and I guess enabling taint mode isn't in that category.
I wonder what bugs taint checking wouldn't catch, that this would.