[Voodoo-circle-announce] New CVS release of VooDoo cIRCle

[Ghost V. <gho...@us...>]

Greetings,

There is in the CVS repository the latest stable version of VooDoo
cIRCle IRC bot.

 From ChangeLog:

- Bug fix: POSIX: Possible heap-based buffer overflow when POSIX 
operating system returns human-readable string description of a socket 
error code longer than 1023 bytes. However, it is very unlikely that 
there is an operating system with such long BSD socket API error 
messages. This bug is not critical, and don't affect Windoze users.

- Bug fix: POSIX: In some circumstances, if BSD socket API calls to 
"socket()" and "bind()", an incorrect error message might be logged to 
logs ("socket.log", "cumul.log", if enabled).

- Improvement: Windoze: Implemented all Winsock socket error code 
mappings to error string for human for logs. Strings were taken from the 
latest MSDN to date. All codes are guarded by the preprocessor, so if 
for instance you are compiling the bot on XP, which don't have 
particular V*sta's error, the compilation should succeed.

- Bug fix: Documentation: Fixed incorrect description for "preg_grep" 
built-in function (copy-and-paste error).

- Bug fix: When there were exactly same bound events via "bind" 
procedure command/built-in function, call to "unbind" procedure 
command/built-in function with the same arguments killed only first 
bound event in particular module, not all of them. This affected both 
standard modules and binary modules.

- Improvement: New procedure commands/built-in functions "bind_ex" and 
"unbind_ex". See documentation.

- Change: Increased BOTNET protocol version from 1008 to 1009, as new 
procedure commands were added. Backward compatibility of BOTNET protocol 
is of course kept. This change is only required in case you run older 
bot on BOTNET (protocol version 1008), to force rejection PUSH 
replication of procedure(s) containing these new procedure commands to 
older bot on BOTNET (protocol version 1008 or less), since the 
replication would fail by error entries in "botnet.log" (if enabled). Of 
course, this case is only possible if you set replication rule PUSH or 
PUSHPULL on procedure containing these two new commands to older bot (of 
BOTNET protocol version 1008 or less).

- Change: Increased "VDCMOD_API_VERSION" from version 4 to 5, in 
interface to binary modules, as there are new API functions for 
"bind_ex" and "unbind_ex". Backward compatibility is of course kept; you 
don't need to recompile your binary modules, unless you want to use 
these new API calls. NB: If you wish to use these two new API, you need 
to replace "vdcmod.h" file [API interface for binary modules to call 
bot's (new) API functions of bot] in you binary module by the new one 
that is in bot source package in CVS and/or distribution. Hint: If you 
are unsure whether you are using right/new include file, open "vdcmod.h" 
API interface file in your binary module and plain-text-search for 
string "#define VDCMOD_API_VERSION", and on the same line there should 
be number "5".

- Bug fix: Memory leak when "on_flood" event is triggered and there is 
bound event "flood@channel" via procedure command "bind" or built-in 
function "bind()".

- Bug fix: Memory leak when built-in function "dispatch()" was used.

- Bug fix: "fread" function in built-in function scripting was 
malfunctioning on 64 bit platforms.

- Bug fix: If module with '#version 3' at begining of 'logic.txt' 
without mandatory '#eof' at the end (required for version 3) was tried 
to load (which is failure), there were memory leaks (forgotten to free 
compiled microcode of built-in scripting functions).

- Bug fix: Remote execute call to other bot on BOTNET sent badly-encoded 
data (thus rejected on remote side) if there were multidimensional 
arrays with long depth [important line of code was commented-out (?!)].

- Bug fix: Parser of built-in function scripting parsed erroneous 
expressions e.g. '$x+=2 $x++' as thought it were '$x+=2; $x++;' and 
'$x=array( array(1,2) array("a","b") );' as '$x=array( array(1,2), 
array("a","b") );' and a like. Now sanity is checked.

- Improvement: Sanity checker to parser of built-in function scripting 
was implemented, now it prints some warnings for strange expressions 
like '$y=$x[SEEK_SET];', or generates an error while compiling for 
'$x=3++;' - so far an error occurred at execution/run-time, not at 
compile time.

- Improvement: Internal function scripting parser: Minor speed and 
memory optimization for "switch()"'s "default:" case label.

- Improvement: Cosmetical changes: No warnings for "release" build (i.e. 
without debugging support) on MSVC 9 ("/W4" switch), less warnings and 
remarks for Intel(R) C++ compiler 10.1.022 for Windows, for compile with 
x64 and x86 profiles ("/W4" switch).

- Improvement: Little speed gain after compiling built-in scripting 
procedures and functions - after successful module load (commented-out 
old ineffective code - it was odd as other algorithm was implemented in 
the past).

URL of the project:
http://voodoo-circle.sourceforge.net/

CVS instructions:
$ cvs
-d:pserver:ano...@vo...:/cvsroot/voodoo-circle 

login

$ cvs -z3
-d:pserver:ano...@vo...:/cvsroot/voodoo-circle 

co -P voodoo-circle-src

(two commands on two separate lines; on first command, when asked for
password just hit ENTER/RETURN - an empty password)

Don't forget to:
$ chmod a+rx ./configure irc_bot/configure sendmail/configure \
       vdcsvc/configure irc_bot/selftest_eval-test-1.sh

With best regards,
VooDooMan
VooDoo cIRCle project
.