On Wednesday 01 August 2001 13:29, Phil Driscoll wrote:
>Every warning message you get represents an
> opportunity for a malicious user to find a secutiry hole in your code.
Oops - I meant to say 'security hole' - I wish both my hands would type at
the same speed :)
--
Phil Driscoll
--
PHP Gen
On Wednesday 01 August 2001 09:21, Chris Fry wrote:
> Just set warnings to off in your php.ini - it's on by default
NO NO NO!
On your development machine, set your warning levels to E_ALL in php.ini, and
then fix your code! Every warning message you get represents an opportunity
for a malicious
Just set warnings to off in your php.ini - it's on by default
Chris
Melania Popescu wrote:
> I have a lot of php scripts developed with php3.
> I've installed php4 and I get some warnings when I
> evaluate variables there are not set (are empty).
> In php3 there was no problem (no warning).
> I
I have a lot of php scripts developed with php3.
I've installed php4 and I get some warnings when I
evaluate variables there are not set (are empty).
In php3 there was no problem (no warning).
If I modify the code by using empty($var) or
isset($var) it's ok, but there are lots of such
issues.
How
4 matches
Mail list logo