I would like to report a security related bug within ModPerl 2.0.4,
though prefer not to disclose the details to a public channel.
The appropriate secure channel for all ASF related security vulnerability
reporting is the closed list, secur...@apache.org, which will be triaged
to the appropriat
Dear Sirs,
I would like to report a security related bug within ModPerl 2.0.4, though
prefer not to disclose the details to a public channel.
The bug was found on a customer's Linux based system, and further confirmed on
a test bed system which was set up running ModPerl 2.0.4 and Apache 2.2.8
On Mon, 2009-02-23 at 15:32 +0100, Clinton Gormley wrote:
> Hiya
>
> I'm using PerlConfigRequire to load my Perl application, which also sets
> up the VirtualHost's using $r->add_config()
>
> The problem is, if one my modules has a compile time error, instead of
> getting the real error message,
I decided to update my apache configuration to include modssl which I
left out of the original installation in 2005. Evidently I don't have
openssl headers
on the server so I guess it is time to reinstall everything. The
problem is that this is a substantial site with a lot of use and I don't
On Thu 26 Feb 2009, Clinton Gormley wrote:
> > Why don't you do that in a block?
>
> How is this different from doing it in the startup.pl file?
Yes, I see, the 2nd run of the code doesn't have STDERR either.
So, you can open a startup logfile in perl and override
CORE::GLOBAL::warn/die or i
