NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Googling for bugs (Score:2)
Reply to This
Re: (Score:1)
Re: (Score:2)
Re:Googling for bugs (Perl CGI injection attacks) (Score:1)
And param() injection attacks [google.com] for Perl, as heard in a Birmingham 2006 talk by MOCK and regurgitated on Perlmonks [perlmonks.org].
Management summary: Don't use foo => $q->param(), to fill a hash if you care about the other values, like is_admin => 0.
Re: (Score:1)
First use.perl.org lesson - you can't edit your comments. More injection attacks [google.com], this time via foo => param(
Re: (Score:2)
Um, yeah. We don't want you to be able to go back and change history and prevent us from seeing what you said. Makes you take more responsibility for it, among other benefits. :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re: (Score:1)
Out of curiosity, why, then, can we edit our Journal entries?
Re: (Score:2)
I've always wondered that myself.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers