This is mainly a bug fix release of version 2.0. There was an issue with running WebKnight 2.0 on systems that are non-Latin (like Korean). This is fixed in this release and users running version 2.0 are strongly recommended to upgrade to this version. Version 1.3 and below is not affected by this bug. You can now also exclude certain IP addresses or ranges from scanning. A new version of the log reader application and updated robots database is also included in this release.
WebKnight 2.1 다운로드 http://www.aqtronix.com/?PageID=99#Download
invalid-fileWebKnight 관련 메뉴얼 PDF 문서
invalid-file설치 동영상
http://www.krcert.or.kr/firewall2/fwDown2.jsp?fkind=13
invalid-filehttp://www.aqtronix.com/ 에서 WebKnight 2.1 이 발표되었습니다
WebKnight 관련 문서도 같이 올립니다 메뉴얼을 보고 사용하는게 좋습니다 안그러면
정상적으로 서비스되어야할것도 블럭이 되어버리거든요
제가 사용해봤을때 느낀점으로는 처음에는 설정사항은 적용하되 실제로 막지는 않고 로그에만 남기는 옵션
이 있습니다 그걸 체크해서 정상적으로 서비스 되어야할 서비스들이 잘 되는지 확인하고
그리고 블럭이 되어야하는 것들이 블럭이 되는지 몇일간은 로그분석만 합니다 그런뒤 잘 된다면 적용을 시키는
것이지요
이렇게 안하고 그냥 적용만 시키면 된다고 생각하면 안됩니다 서비스를 돌리는 형태나 그 서버나 서비스의
제약조건등은 모두 다 틀리니까요 그에 맞게 셋팅을 해야만 합니다
How to install
Installation in IIS with Windows Installer: (for IIS 6.0 see note below!)
Double click the file WebKnight.msi. This will launch Windows Installer and install WebKnight on the local machine. This method will install WebKnight as a global filter on the local machine. If Windows Installer is not installed on your system, you can download it directly from Microsoft:
Windows Installer 2.0 Redistributable for Windows NT 4.0 and 2000
Windows Installer 2.0 Redistributable for Windows 95, 98, and Me
Installation in IIS with scripts:
To install/uninstall WebKnight on the local or remote machine you can use the file install.vbs/uninstall.vbs from the setup folder. This method will install WebKnight as a global filter on the selected host or localhost.
Manual installation as a global filter in IIS:
- Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight).
- Open the IIS snap-in.
- Right-click the server name (not the site name) (in IIS 6 right-click Web Sites) under Internet Information Services in the MMC, and then select Properties.
- Verify that WWW Service is displayed in the Master Properties drop-down list, and click the Edit button. For IIS 6 go to next step.
- Choose the ISAPI Filters tab, and then click the Add button.
- In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
- Select OK to close each dialog.
- Review any settings of WebKnight, by running config.exe that you copied locally.
- Restart IIS.
Manual installation as a site filter in IIS:
- Copy all the files in the Setup folder to a local folder on the server (e.g. C:\Program Files\AQTRONIX WebKnight\W3SVC1). Note: it is important to have a unique folder for each WebKnight installation!
- Open the IIS snap-in.
- Right-click the site name (not the server name) under Internet Information Services in the MMC, and then select Properties.
- Choose the ISAPI Filters tab, and then click the Add button.
- In the Filter Properties window, type WebKnight, and enter the full path to WebKnight.dll in the Executable box.
- Select OK to close each dialog.
- Review any settings of WebKnight, by running config.exe that you copied locally. (Make sure global filter capabilities are disabled: uncheck 'Is Installed As Global Filter')
- For IIS 6 you need to make sure that each site for which you installed WebKnight as a site filter, has its own application pool. This is because only one instance of WebKnight can be run in any application pool. By default all sites are run in the DefaultAppPool and can only contain one instance of WebKnight, so you can only have one site filter, unless you specify a different application pool for any additional site on which you are running WebKnight as a site filter.
- Restart IIS.
If you want to import your settings from urlscan, you can do that by copying the file urlscan.ini to the WebKnight directory. Delete WebKnight.xml (or rename it) and your settings from urlscan.ini will be imported in a new WebKnight.xml file when you restart your web server. This can be useful if you experienced problems with your urlscan installation and you had to customize the settings of urlscan and want to keep using these settings. If you want to load the default settings again, you can do that by deleting the files WebKnight.xml and urlscan.ini in the directory WebKnight and a new WebKnight.xml will be made with the default settings when you restart your web server.
Installation in IIS 6.0: to run WebKnight as a global filter in IIS 6.0, you have two options:
- Run IIS in IIS 5.0 Isolation mode (recommended)
- Continue running IIS in worker process mode but without the global filtering capabilities of WebKnight, and you need a unique log file per process. So you have to make sure you:
- uncheck 'Is Installed As Global Filter' under Global Filter Capabilities
- check 'Per Process Logging' under Logging (each application pool will load its own instance of WebKnight, if you only have one pool, this is not required.)
- Make sure the account NETWORK SERVICE (or whatever account(s) you set the application pool(s) to use) has change permission on the WebKnight folder and subfolders
- Restart IIS after doing the above changes.
Non-IIS: Look at the documentation of your web server (Note: only web servers with ISAPI filter support can run WebKnight).
| Published: 20/08/2002 | Document Type: General |
| Last modified: 9/10/2007 | Target: General |
| Visibility: Public | Language: English |
ntfaq.co.kr 에서 가져온 WebKnight 관련 PPT 와 대모시연 동영상입니다
'유용한_팁' 카테고리의 다른 글
| Microsoft Windows XP Service Pack 2 - WGA Patch (2) | 2007.11.05 |
|---|---|
| FreeBSD 계정 수정하기 (0) | 2007.11.04 |
| Dumpchk.exe를 사용하여 메모리 덤프 파일을 검사하는 방법 (0) | 2007.11.02 |
| Microsoft Windows 2003 Server 최적화 설정하기 (0) | 2007.11.01 |
| META 태그 사용법 (1) | 2007.11.01 |
댓글