Masking or anonymizing a Web server involves removing identifying details that intruders could use to detect your OS and Web server vendor and version. This information, while providing little or no utility to legitimate users, is often the starting place for crackers, blackhat hackers and "script kiddies". This article explores some ways you can minimize the risk of such detection. Most of the examples focus on Microsoft’s Internet Information Server (IIS), since it has been most widely lambasted for its vulnerabilities, but some Apache detection countermeasures are also covered. While IIS users probably have the most vested interest here, server anonymization is relevant to anyone responsible for administering a Web server.
A senior IIS admin shares his experience and describes top 10 things to do to improve IIS, which are "Customize Your Error Pages", "Dive into the MetaBase", "Add spell checking to your URLs", "Rewrite your URLs", "Add browser detection", "Gzip site content", "Cache your content", "Tune your server", "Secure your server with simple fixes" and "Patch, patch, patch!".
Before you can test Active Server Pages on your development PC, you need a web server. This article gives step-by-step instructions (literally) on how to install and configure Microsoft's Personal Web Server on Windows 98.
A step-by-step article on creating the functions and ASP files you'll need to schedule and monitor tasks remotely on your server. Using ASP, SQL Server, ASPExec, and the Windows Scripting Host, it provides a brief description of each of the steps involved.
0.0