On Tue, Feb 21, 2012 at 6:55 PM, Cees Hek wrote:
> On Mon, Feb 13, 2012 at 11:58 PM, Aaron Knister wrote:
> > Hi Tuomo,
> >
> > I don't mean 80,000 virtual hosts. I have over 80k unix accounts for
> which content is being served via mod_userdir. And I consider eac
s in part exactly for the reasons you
specified. The other issue is the potential for suexec abuse. I only have one
perl access handler I need to use and it has no global variables.
Sent from my iPhone
On Feb 13, 2012, at 3:55 AM, Tuomo Salo wrote:
> On Fri, Feb 10, 2012 at 08:50:21A
cally, the directives I would like to prevent are:
Perl*Handler
Perl*Var
Perl*Env
PerlOptions
PerlModule
PerlRequire
Pretty much any directive defined with the MP_CMD_DIR_* macros.
-Aaron
On Sat, Feb 11, 2012 at 6:29 PM, Perrin Harkins wrote:
> On Fri, Feb 10, 2012 at 6:46 AM, Aaron Kniste
On Friday, 10 February 2012 06:46:01 Aaron Knister wrote:
>> I was thinking of something along these lines:
>>
>> A per-directory config directive called PerlHtaccessOverrides with possible
>> values of Handlers, Others, Env, Options, All and None. These names are
>> ba
20 AM, Dave Hodgkinson wrote:
>
> On 10 Feb 2012, at 11:46, Aaron Knister wrote:
>
>> Hi,
>>
>> I'm using mod_perl in a shared hosting environment for some server-side
>> configuration bits. All dynamic content for the users runs through SuEXEC,
>> h
likely to be accepted upstream :)
Thanks!
-Aaron
--
Aaron Knister
Systems Administrator
Division of Information Technology
University of Maryland, Baltimore County
aar...@umbc.edu
