in reply to Re^2: How to make that works with perl
in thread How to make that works with perl

Potential black hats don't have access to the error logs either. Leaving development error output may let out something you don't want being leaked to potential attackers. Set up your web server to send an innocuous error page and leave the detailed errors for the developers' eyes only.l

Replies are listed 'Best First'.
Re^4: How to make that works with perl
by naikonta (Curate) on Apr 14, 2007 at 06:57 UTC
    You're right :-) I was actually thinking about for internal scope applicaitons only, but I neglected to even mention it. But even then, the black hats remain such a worry in a very big organization. There was also a mix and match but proved to become "mismatch" when I put the "unless" clause. I should have stressed that I prefer the sophisticated (which is freely translated to user friendly) error message instead of the usual 500 ISE page for public apps for neither harmful nor hintful.

    Thanks for remind me that :-)

    Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!
[reply]

In Section Seekers of Perl Wisdom