MESSAGE
| DATE | 2014-09-15 |
| FROM | Ruben Safir
|
| SUBJECT | Re: [NYLXS - HANGOUT] Apache Security tips
|
On 09/15/2014 03:24 PM, Chris Knadle wrote:
> Nobody is good enough to make their own package "cold"; there's work going on
> within Debian to try to get to the point where this is possible for /simple/
> packages, but for non-trivial packages I don't know anybody that could start
> from scratch and make a good package.
I'm trying to fix something that I can GUARANTEE you that the debian
package
developers wouldn't know their ass from their elbows deep into the code of
modperl and your prostylizing me utter bullshit, Chris.
I will never use a Mac because their shit is Broken
I will never use Debian because their shit is broken
So now you can tell someone else how great debian is.
And yes Chris, if I wasn't lazy, I would set my apache configuration in
my own package, like many other sysadmins so. But apache's core
packaging is
so good and so flexible, that I don't see the point.
I need to know how to hand off a perlresponsehandler modperl module to
the apache
indexes module because a simple decline doesn't pick up the fancy indexing
in the apache response cycle. Traditionally modperl guys get around this
problem by attaching their scripts to in httpd.conf
I need this to work on the entire directory tree without losing fancy
indexing.
That is what I need to KNOW. If you know that answer, fine. If you
don't then
don't blow smoke at me.
Finally, I sent that article out because I thought it had some good and
valid information
in it on securing your webserver through apache rewrite.
Ruben
|
|
