MSDN Archive Home
Help and FAQs
All Resource Updates
Change History (all pages)
Resource Page Description
The ActiveX "killbit" has been in the security news lately, and I've always been mystified by how the 'killbit' works. Then I read an article in one of Microsoft's blogs that went into great detail about the ActiveX "killbit" and how it's actually configured and used (http://blogs.technet.com/swi/archive/2008/02/06/The-Kill_2D00_Bit-FAQ_3A00_-Part-1-of-3.aspx). And even further, Robert McLaws' blog article "IE8 and "Killbits'" (http://www.windows-now.com/blogs/robert/ie8-and-killbits.aspx) gave me the incentive to think of this as more than just a propellerhead problem.
Once I had that information in hand, and mostly because I was looking for a new challenge for my growing coding skills, I decided to write a .NET GUI app that would allow me to see which ActiveX controls had been "killbit'ed" (as well as explore all those ActiveX controls that were candidates for the "killbit").
I've left room in the application to be able to enable editing of the killbit (turning it on for additional controls, as well as *potentially* turn it off for already-"killbit'ed" controls), but in its initial form it's just a read-only exploration tool.
If you like it, and would like it to be enhanced in some way, let me know by posting a new Discussion or Issue in the project space. If you'd like more details on how it was constructed, ask away and I'll post explanations as answers (and as a way to document it as well).
**Delete the following note before publishing **
This resource page is currently in setup mode and only available to coordinators and developers. Once you have finished setting up your resource page you can publish it to make it available to all MSDN Code Gallery visitors.
To get your Resource Page ready to publish, you should do the following:
Make any changes to the details of your resource page
Here you can enable or disable functions of your resource page. You might want to turn on the Issue Tracker to allow users to provide feedback on your resource, or if you have a resource that does not involve a code sample, you may want to turn off the Releases tab.
Make sure your resource page description is detailed enough to let people search for your resource.
Add your code sample or other resources to the resource page
If you’re uploading code, go to the Releases tab and create a new release to house your code. Creating a release allows you to have the license properly displayed when people download your code, as well as provides a download count.
Edit your Wiki page to attach any resources you may have that are not source code.
If you want to let someone see your resource page before it is published, go to the People tab and add them to your resource page
This will let you add other team members who may be contributing to your resource, or just show it off and get feedback from someone you trust.
Tag your resource page with descriptive tags to make it easier for people to find your resources when browsing the gallery.
Publish your resource page so it becomes visible to everyone!
Additional information on starting a new resource page is available here:
Resource Page Startup Guide
Jul 21 2008 at 10:02 AM
, version 1
Sign in to add a comment
Killbit Explorer v1.0 ...
Mon Jul 21 2008 at 7:00 AM
More Tags ...
Visual Studio 2005
Visual Studio 2008
Visual Studio 2010
Manage Your Profile
MSDN Flash Newsletter
© 2008 Microsoft Corporation. All rights reserved.