RE: [NeoStats-Devel] [Commits] r159 - branches/3.0/libopm

> 
> Justin Hammond wrote:
> > Well, considering it was broken before as well... :)
> 
> As mentioned on list and the forum on more than one occasion, 
> I have been
> running 3.0 in production for some time so that I have a 
> running real life
> test on each update. Thanks to libevent I have not been able 
> to update this
> since it would remove my ability to run OPSB. OPSB was broken 
> due to the
> premature introduction of libevent which is a different issue 
> to the current
> status where even configure fails. :(
> 

If you look at the changes made, I've removed libopm from OPSB. Previously
libopm handled a lot of the socket code/read/write etc etc and with the
introduction of libevent and the socket update, was very much duplicating
what we have now introduced. This really only struct me when I was working
through the libopm code trying to figure out the best way to have it support
libevent... I realised that we can do it with a lot less work and
duplication.

What I commited tonight is not complete. Its 90% there. I have to write the
actual proxy protocol support and read functions, but its not a huge amount
of work. The remaining work is around just cleaning up after scans, and
should be trivial to do.

You might also notice that I removed the dns blacklist support from OPSB.
This is partly due to the fact that people want to have multiple DNS
blacklist support, so intend to write a separate module for this as well...
(since it will no longer just be tied to Blitzed OPM list, its not necessary
proxy specific anymore, some might want to use the TOR or spam lists as
well)




> > My homedrive is giving me smart errors, so I'm scared to 
> > leave anything on it at the moment that isn't backed up. This 
> > is work in progress. 
> 
> I know it is work in progress but based on your emails I was under the
> impression you were fixing up socket stuff including opsb and 
> implementing
> the config stuff last weekend. Is any of this going to happen 
> any time soon?
> 

The customers that pay the bills for the servers that host the NeoStats
infra come first... Sorry, but if I don't keep them happy, then I got bigger
problems than just a hard drive failure. I'll be putting in a couple of
hours each day this week on each (opsb and config)