Re: diff for custom scanner protocols

On Thu, Jan 29, 2004 at 11:17:58AM -0800, winkey wrote:
> here is a propper diff i think

OK so basically all you have donme is added 1 extra protocol called
"customer" but then added a config option that lets you choose what
BOPM sends, so that your protocol can be customised for lots of
trivial other protocols.

It's not a bad idea but it has some limitations, namely:

- You can't talk in a binary protocol with the thing you're testing
  because there is no way to include nulls in the send_string.

- You can't do any more validation than just sending one string and
  waiting for another, which rules out more complex protocols and
  stops you from doing a few extra checks.  I think I put a bunch
  more checks into the mindjail protocol just to be absolutely sure,
  but this wouldn't be possible with this patch.

- You can't craft a dynamic send_string so any non-trivial protocol
  probably can't be used - SOCKS commands have to be constructed.

It might not be a bad idea to incorporate into the main BOPM if we
could solve some of the above, but other than that, writing new
protocols is really easy with BOPM anyway.

I was working on making BOPM modular so that protocols could be put
in .so files and loaded via config commands.  Got it pretty much
working, just need to find time to work out the flex/bison bits.

-- 
Andy Smith -- Occasional BOPM Developer And Support Monkey.  Please copy
all BOPM support queries to the BOPM list, _not_ just directly to me!
If I've helped you with BOPM then please check my wishlist!
http://www.amazon.co.uk/exec/obidos/registry/23IJ4U7N4J3X9