I'd say the correct solution isn't to control which modules can accidentally untaint data (it seems pretty likely that no matter what we do, maliciously coded modules will be able to screw you over if they try to do so intentionally) but rather fix those aspects of tainting that allow any module to accidentally untaint data. Personally, I think untainting data should only be the result of an explicit "untaint" function, but maybe that's going too far. -- Adam Lopresto ([EMAIL PROTECTED]) http://cec.wustl.edu/~adam/
Her hair glistened in the rain like nose hair after a sneeze. (Chuck Smith, Woodbridge)
