The site is currently in read-only mode for maintenance. Posting of new items will be available again shortly.
This article gives out a sample showing how to develop Browser Helper Objects/Internet Explorer Object and how to deal with IWebBrowser2.
This sample, IEGuard, has the similar functionality of Microsoft Internet Explorer's Options / Content Advisor/Approved Sites. It can real time monitor the Internet Explorer web browse activities, and only those allowed web sites can be visited and other web navigation will be stopped. A tool, IEGuardMan, is given with this sample to set up the job criteria of IEGuard.
IEGuard can easily be updated to the software for MS Internet Explorer Web activities, monitoring and tracking.
The Problem on making Windows/Internet Explorer failure.
In IEGuard, a lockout test is given to test the way to disable Windows Explorer/Internet Explorer. When lockout test is processing, all activities related to Windows Explorer and MS Internet Explorer are locked out and Windows system is functionally failed partially.
In the worst case that Lockout flag is enabled, IEGuardMan is closed and you can run the batch file restoreOS.bat or command file restoreOS.cmd, which are given within the sample code, in MS-DOS Prompt/Command Prompt to un-register the IEGuard component from system and restore Windows functionality.
Microsoft ties Windows Explorer and Internet Explorer together with IWebBrowser2, it also give a way for the potential virus to attack to Windows system by canceling all IWebBrowser2 instances when those IWebBrowser2 objects are instantiated like the Lockout test in IEguard did. It is a bad derivative of IWebBrowser2.
Reference and technical detail about BHO.
For more information about BHO, you can get it from Dino Esposito's article "Browser Helper Objects: The Browser the Way You Want It" in MSDN.
The primary purpose about this article.
IWebBrowser2 has been a key technology in MS Windows system, so
- I hope Microsoft can pay attention on the problem of the hole of IWebBrowser2 pointed out in this article.
- Or otherwise, somebody can develop a MS Windows “Predator” program (or you can say it as "Virus") to squash the Windows system by borrowing the idea in this article. That would be the best prize for this article.