Some bug fixes

I added some checks to cas to prevent segfaults (someone should port it to C++...), added an option to specify the location of the amuleweb binary for autostart and fixed the wxCas save dialog.

lfroen removed mutexts from amuleweb as we don't use threads anymore.

amuleweb-assert, php-standalone, compat

With developers either desperately lacking time and/or not feeling like working during the summer vacation only few changes occured during my absence.

aMuleweb gained support for creating basic backtraces on crash (just like aMule does, but using gdb is still necessary to properly identify problems). I think Vollstrecker, phoenix and GonoszTopi worked on this.

Lfroen changed the build process to allow for php standalone compilation.

GonoszTopi committed some patches to improve compatibility with different shells.

All quiet on the southern front

whilst I haven't updated lately (I blame flower vendors.), there have been some changes to aMule.

It was mainly Vollstrecker going on a patch spree and changing everything which had no svn lock on it.

He worked on Copyright messages, po file encoding, fixed make clean and make distclean (fixing a real bug) and updated the debian folder.

Myth contributed a patch for Feedback from shared files while morph had a look at our man pages.

Oh, and we made a release. But I think you know that already.

amuleGui, Windows Resource leaks, SX

Thanks to xor the amuleGUI desynchronization should be fixed now in 2.2.2 and SVN.

Also Stu Redman was working on fixing GDI resource leaks on the Windows build which should improve long term stability on Windows. (Hopefully this can be fixed on wx side, too.)

Muleview supports now v3 nodes.dat files, thanks to a patch by GonoszTopi.

At last, Kry committed a fix for incorrect source exchange packets.

Kad bugfixes and improvements.

GonoszTopi made more improvements to the aMule Kad implementation. (Will be included in 2.2.2)

• Implemented a special nodes.dat version, which is more suited for mass distribution without causing significant additional traffic for the included nodes. This is to allow eMule to add a nodes.dat to the installer, so that new user can connect to Kad without having to connect to servers or downloading a nodes.dat themself. We also need to be able to read and process this nodes.dat file.


• Implemented an alternate method to estimate the total user count in the Kad network, which is not based on our local routing table. It is experimental and only in trunk.


• Fixed a minor bug with kad obfuscation when contacting answering unbofuscated hello-requests.


• Made sure that only one challenge to verify a contact is sent at a time to the same IP.