Release Notes: The code was updated to support NeoStats 3.0 Alpha 3. The DNS blacklist code was split out to a new module, BLSB. Several issues regarding NeoStats consuming 100% CPU when using OPSB have also been corrected. gcc 4.0 support was fixed.
Release Notes: This release fixes compile errors with newer versions of GCC.
Release Notes: This release added the ability to bind the outgoing scans to a specific IP address if configured in the configuration file.
Release Notes: This release fixes the problem with OPSB broadcasting out that it is not configured after a reload, and fixes problems with some SET variables not being retained after a restart.
Release Notes: This release adds a SET interface to control OPSB's nickname, etc., an option to make OPSB less verbose, compile fixes for older BSDs, fixes to the exceptions list being case-sensitive, and the ability to take advantage of IRCds that provide the users' IP address instead of performing DNS lookups for every connection. It fixes a problem with OPSB being configured with DISABLESCAN and the scan queue growing out of control.
Release Notes: This release fixes a bug with socks 5 scanning that would not correctly identify open proxies using the socks5 protocol.
Release Notes: This release contains minor bugfixes, and it updates the documentation and online help with new commands that were missing from the previous release. This marks a stable release of 2.0.
Release Notes: OPSB now uses the Blitzed Open Proxy Monitor Engine to scan users for Open Proxies. The Large log files on BSD platforms have been fixed. The documentation was updated to reflect the new options and configuration.
Release Notes: This release fixed most bugs and added the option to remove A KILLS set by the program on your network. Extra information is included in the AKILL message about the port and type of ope n proxies found, and some additional performance statistics wer e added. NeoStats 2.5.2 is required.
Release Notes: A buffer overflow that was trigged by HTTP proxies was fixed. Problems which occurred when opsb was configured to only do a DNS blacklist lookup instead of performing the actual scan were fixed.