Re: interpreting Nessus scan results | TRACE & TRACK?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 interpreting (and hoping for some 'interpretative guidance' here). It suggests using a rewrite to handle the issue (something I've never done). I'm also not entirely sure of what TRACE and TRACK do?


The nessus text tells you exactly what they are for, and how to disable them.


--
J.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux