I think that most Embperl issues are really just Perl issues. I think
one can avoid most problems by making sure that the user input is
checked for double/single quotes, and backticks. Also I think it is good
if you don't interpolate any user data, by putting the input in double
quotes, or some ot
>
>I have been doing final security checks before bringing a website live --
>making sure that users can't manually enter post data to see things they
>shouldn't. My employer is naturally curious about any security issues that
>tend to aflict embperl/mod_perl/cgi. While we have followed common sen
>>$obj, as you use it above, is intented if need an second object with
>>different inherece hierachie. Also you can store data in $obj, it is only
>>available to the pages that have access to $obj, so you have to store $obj
>>somewhere, e.g. in $req -> {obj}.
>I wonder I do not understand
>
>can
>Having upgraded to embperl 2.0b3 I find masses of logging in
>/tmp/embperl.log despite having EMBPERL_DEBUG set to 0 (and EMBPERL_LOG set
>to /dev/null). Has anyone else experienced this or know how to stop it?
>
This are some debug message for me. They will go away with the next release.
Un
