Using A Rule Engine For Hacking

March 17, 2010

I was interested to stumble upon an issue of the hacker zine Phrack dating back to 2000 which includes a tutorial on building a vulnerability scanning system used for hacking…that includes a rule engine. The article mentions a number of things you would expect: Rete, OPS5, CLIPS, Charles Forgy, Daniel Miranker and even the monkey and bananas problem.

Monkey and Bananas 2: The Revenge

October 31, 2008

If you’ve read Charles Forgy’s dissertation or the Brownston/Farrell/Kant/Martin OPS5 book or any of a number of resources, you eventually come across the Monkey and Bananas ruleset.

Some time ago, I stumbled across a humorous AI exam which contains a “complicated” form of Monkey and Bananas:

The monkey and bananas problem has been complicated by the following additional factors :
(i) The bananas will not be ripe for two weeks.
(ii) The monkey is blind.
(iii) The bananas are locked in a safe.
(iv) There are no suitable boxes present.
(v) The monkey is afraid of heights.
(vi) The floor of the room has been electrified.
(vii) The monkey doesn’t like bananas anyway.

assert (monkey); assert (bananas);

October 30, 2008

After a number of years working in the rules space, I am overdue to participate more directly in the online communities. Apologies to KSK, since I turned him down when he asked me to do this years ago. 

My area of focus at work is broader than rules, and this blog will head into that space at some point. However, the initial content will be exclusively rules.

I’ll do what I can to provide regular content.

The standard disclaimer in the About page applies to everything here.