But in the context of taint checking w/ CGI, isn't the main
point just that you should scrub your CGI parameters??
Your web server should not be set-UID to root so the security
problem is that stuff from "the world" needs to be checked.
So isn't a reasonable solution as simple as replacing
the few CGI.pm methods that get data from the client with
versions that require "scrubbing instructions"? I'd
probably make a tiny hack to CGI.pm to prevent it from
being used directly and then make a CGI::Safe where
the param() method is a fatal error but safeparam() requires
an extra argument that is the scrubbing instructions.
I'd support a few formats of scrubbing instructions. You
should make the most common case of requiring the parameter
value to match /^\w[-\w.]*\z/ be very easy.
But if a ref to a regex is provided, then apply the regex
and die if it fails, return $1 if successful. If a code
ref is provided, just run that code.
(but my friends call me "Tye")
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||