in reply to Re: [5.8.0 Note] use Taint or die
in thread [5.8.0 Note] use Taint or die
It is, however, significantly better then nothing, esp. if used properly. Specificly, you should "use Taint" before even looking at possibly tainted data, as far as you can get away with it. If it's the second line in your file (after the shabang), that's a very small window to mess things up. Additionaly, unless you advertise it (such as by using CGI::Carp :fatalsToBrowser), they won't know you're using the Taint module, and thus not design their crack to account for it. Essensialy, the only attack left is to try to mess up PERL5LIB (or possibly PATH with a tainted perl binary) before perl is invoked. It's not a bullet-proof-vest, just bullet-resistant. Still better then nothing. (The /best/ thing to do would be to have die "INVOKED WITHOUT TAINT!" unless ${^TAINT} directly as the second line of your script.
PS -- does anybody know what ${^TAINT} is set to in "baby taint mode" (IE -t, warn on taint violation mode). I'm running 5.6.1, which doesn't support either. It might be possible to fake out ${^TAINT} checking with -t.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: [5.8.0 Note] use Taint or die
by particle (Vicar) on Nov 30, 2002 at 02:06 UTC | |
by theorbtwo (Prior) on Nov 30, 2002 at 02:29 UTC | |
|
Re: [5.8.0 Note] use Taint or die
by Abigail-II (Bishop) on Nov 30, 2002 at 15:47 UTC |