I didn't see this thread. I commented on Firekeeper in another forum already, namely that I don't see anything useful coming out of it. If you look at Firekeeper's list of rules, it is mostly vulnerabilities in Internet Explorer and plugins. There is little point in looking for Internet Explorer exploits from Firefox of course, but same goes for plugin vulnerabilities - Firekeeper only attaches to the traffic of the browser, it cannot filter the data plugins load!
There is more. The list of rules is compiled from published vulnerabilities. Now if a critical vulnerability in Firefox is published it is mostly after it has been fixed. If it hasn't been fixed yet it will be fixed soon, two weeks at most. For Firekeeper to be useful it needs to get a rules update significantly faster than a new Firefox version is released - otherwise keeping your browser updated will work just as well (but far less annoying). And the new rule should be general enough to catch at least small variation of the attack (the rules I have seen aren't).
I have seen only one general rule in Firekeeper - "document.domain". Good luck with that. I disabled tried to disable document.domain via
CAPS and it broke several major sites (that was my intention, I wanted to find out who used it). Mind you, I only disabled setting this property while Firekeeper will be triggered by any reference to it - even if it is only a documentation text.
