System - Security - Hacking

Securing Apache web server is very important, it means allowing see only the intended info & protecting data and restricting access. Some hints and tips on security issues in setting up a web server. Some of the suggestions will be general, others specific to Apache. 1. First, make sure you've installed latest security patches If you have obtained your version of the HTTP Server directly from Apache, we highly recommend you subscribe to the  Apache HTTP Server Announcements List  where you can keep informed of new releases and security updates. Similar services are available from most third-party distributors of Apache software. 2.  Hide the Apache Version number, and other sensitive information. By default many Apache installations tell the world what version of Apache you're running, what operating system/version you're running, and even what Apache Modules are installed on the server. Attackers can use this information to their advantage when performing an att

The Apache HTTP Server is designed to be a powerful and flexible web server that can work on a very wide variety of platforms in a range of different environments.  A pache2 comes with 2  multi processing modules (MPMs) which are responsible for binding to network ports on the machine, accepting requests, and dispatching children to handle the requests.: 1. Prefork 2. Worker What is the difference between this two? Prefork MPM   uses multiple child processes with one thread each and each process handles one connection at a time. Worker MPM   uses multiple child processes with many threads each. Each thread handles one connection at a time. On most of the systems, speed of both the MPMs is comparable but prefork uses more memory than worker. Which one to use? Websites that need a great deal of scalability can choose to use a threaded MPM like  worker  (because of low memory usage)  while sites requiring stability or compatibility with older software can use a  prefork  (