MESSAGE
| DATE | 2014-09-15 |
| FROM | Ruben Safir
|
| SUBJECT | Re: [NYLXS - HANGOUT] Apache Security tips
|
On Mon, Sep 15, 2014 at 09:10:27AM -0400, Paul Robert Marino wrote:
> Rubin
Are you still custom compiling your own copy of Apache?
I would have hoped you would have stopped doing that by now. Its a lot of hassle and a massive security risk if you aren't keeping up with the CVE's
-- Sent from my HP Pre3
On Sep 15, 2014 12:41 AM, Ruben Safir <mrbrklyn-at-panix.com> wrote:
On 09/14/2014 10:21 PM, Chris Knadle wrote:
> On Sunday, September 14, 2014 20:43:05 Ruben Safir wrote:
>> http://perishablepress.com/eight-ways-to-blacklist-with-apaches-mod_rewrite/
>>
>> mod_rewrite
>>
>> Too bad I can't get it to work!
>>
>> It is not a compiled in module.
> The loading of the module needs to be included in your configuration; e.g.:
>
> LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so
>
> -- Chris
>
> --
>
> Chris Knadle
> Chris.Knadle-at-coredump.us
>
that only works if it is compiled
I can't read this, but just what I need for security is 10 levels of
chopped up httpd.conf files scattered in a remote directory
Fuck that ...
In fact, the last debian installation totally fucked up embperl and I
have to not only do apache by hand, but I also had to install Perl by
hand and hack the systems version of perl to be linked into the admin
config.
But just when I though debian juck sucked, then I saw opensuse had the
same trouble. I think there is a bugfix in the latest perl to address
the problems, if I understand what I read.
If I was good, I'd be ablke to write my own package...
I'm not that good.
Ruben
|
|
