Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Perl security done right More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

DBI and TaintIn (Score:2)

by brian_d_foy (44)

I'll add some stuff on DBI and its TaintIn setting for the next edition :)
- Re: (Score:1)
  
  by Aristotle (5147)
  
  Actually I find TaintIn barely useful. I use bind parameters for any user input being put into the database, so there’s no way to do damage there. But TaintOut is very important, because it helps XSS-proofing the code.
  - Re: (Score:2)
    
    by petdance (2468)
    
    so there’s no way to do damage there.
    It's an issue of philosophy, not practicality. You shouldn't be putting anything tainted into a database, where it becomes untainted. It's a big reminder.
    
    --
    --
    xoa
    - Re:DBI and TaintIn (Score:2)
      
      by bart (450) <bart.lateur@pandora.be> on 2007.08.12 12:05 (#56917) Journal
      
      So you're sure no data will ever be put into the database via another route than your app? Rrrright.
      
      Reply to This
      
      Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.