|
|||||||||||
|
Updated URLScan Security Tool Released
From: Eric Johansen <eric.johansen(at)us.ing.com>
Date: Wed May 21 2003 - 11:59:50 EDT
So far I've had little success using the executable provided by Microsoft to "automagically" update my existing URLScan 2.0-running web servers. So I've resorted to extracting the contents of the Setup.EXE (use Setup.EXE /C /T:D:\URLScan_25 for example) and then extracting urlscan.exe (contained in Setup.EXE) using urlscan.exe /X. This extracts all contents to the directory where urlscan.exe is located, so be careful you aren't doing this in your current, live URLScan 2.0 directory unless you want your urlscan.ini to be overwritten with the newfangled one - better to manually edit your ini. Installing manually is easy...drop the new DLL in the old DLLs place (after stopping IIS of course), edit your ini with the new features you want, and then restart IIS. You don't have to take advantage of any of the new features, and I've found that it works great if just plunked into place...and you get that warm, fuzzy feeling that you have the latest and greatest version in place. :) Here are the "new" features from version 2.0 (indicated with ***), which if you are manually editing your urlscan.ini's you should use: (compiled from the above URL as well as the urlscan.ini config file)
***Changing the Log File Directory
Use: LoggingDirectory=D:\LogFiles\URLScan --- ***Logging Long URLs -LogLongUrls Use: (under OPTIONS) LogLongUrls=0 If 1, then up to 128K per request can be logged. If 0, then only 1k is allowed. --- ***Restricting the Size of Requests -RequestLimits -MaxAllowedContentLength -MaxUrl -MaxQueryString Use: [RequestLimits]Received on Wed May 21 13:32:38 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:30 EDT |
||||||||||
|
|||||||||||