- Original Message -
From: egc
Date: Mon, 22 Nov 2010 16:54:44 -0500
Subject: [us...@httpd] interpreting Nessus scan results | TRACE & TRACK?
To: users@httpd.apache.org
Greetings --
Running 2.2.17 on a CentOS 5.5 host. All the usual security tweaks
(or, at least the ones
On 11/22/2010 5:04 PM, Jeroen Geilman wrote:
On 11/22/2010 10:54 PM, egc wrote:
Greetings --
Running 2.2.17 on a CentOS 5.5 host. All the usual security tweaks
(or, at least the ones I'm familiar with) in place. Had our network
types run a Nessus scan against the host - all fine, except for
On 11/22/2010 10:54 PM, egc wrote:
Greetings --
Running 2.2.17 on a CentOS 5.5 host. All the usual security tweaks
(or, at least the ones I'm familiar with) in place. Had our network
types run a Nessus scan against the host - all fine, except for the
following, which I'm having trouble interp
Greetings --
Running 2.2.17 on a CentOS 5.5 host. All the usual security tweaks (or,
at least the ones I'm familiar with) in place. Had our network types run
a Nessus scan against the host - all fine, except for the following,
which I'm having trouble interpreting (and hoping for some
'interp
