0.49a BETA1 ------------------------ April, 12. 2008 ------------------------.: Beta versions now create a small test text file which is shared by eMule to help us debugging protocol changes (esp Kad). On exit this file is deleted.: Fixed a bug with the "Open Directory" menuitem in the shared files window [Stulle]

------------------------ April, 11. 2008 ------------------------.: Added the obfuscation setting to the First Time wizard and removed the full chunk upload setting instead.: Disabled peercache downloads by default (deprecated).: Added a Beta nagging dialog

------------------------ Mar, 30. 2008 ------------------------.: eMule is now aware of windows standby modes and reconnects after waking up [MorphXt]

------------------------ Mar, 18. 2008 ------------------------.: Fixed: File tooltips used wrong font sizes when using customized Windows metrics..: Added: Support for using Windows default fonts for listview and treeview controls in eMule's main windows. This way one can specify larger fonts for almost all eMule lists via the Windows System Metrics. Specify "UseSystemFontForMainControls=1" in "preferences.ini" to enable..: Fixed: Shared directory treeview control lost icons after Windows System settings were changed..: Fixed: Wrong font mapping for some GUI elements in non-Western locales.

------------------------ Feb, 26. 2008 ------------------------.: When deleting more than 50 files the first 50 names are shown in the confirmation dialog [tHeWiZaRdOfDoS].: Fixed a bug in finding the senders of corrupt data which may lead to false positives [DavidXanatos]

------------------------ Feb, 10. 2008 ------------------------.: Kad will now enforce certain limits when adding new contacts to the routing table: No more than 1 KadNode per IP, 2 similar KadNodes (same bin) from a /24 network and max 10 different KadNodes from a /24 network are allowed. This is supposed to make routing attacks against kad more difficult / resource-intensiveYou can still run more than one kad client from a single IP without any problems, they just don't become part of the internal kad routing but still work without any limitations.

------------------------ Feb, 3. 2008 ------------------------.: The download comments dialog has now a direct possibility to edit the comment spam filter, changes are instantly applied to all existing comments.: Clients which sent comments which get filtered by the comment spam filter are now treated like message spammers (banned).: The ed2k: in ed2k-links is no longer case sensitive.: When connecting to Ed2K eMule starts with a random server instead using first on in the server.met. Any sorting, priority, etc. is not affected by this

------------------------ Feb, 1. 2008 ------------------------.: Several changes have been made to improve kads resistance against malicious keyword publishing:.: Kad now keeps track which filenames were published by different sources for the same file and uses the most common name (instead the last published one) when responding search requests.: Same hashs (files) which have different filesizes are now properly stored seperatly instead overwriting eachother.: Kad calculates a rating based on how many different sources publish a file and how many files publishes a source. When responding to a search request, files with a rating below a set limit will be sent last in order to avoid that spammed files push out valid ones..: The Kad rating for published files is also sent in search results to be used in the future version as indicator

------------------------ Jan, 16. 2008 ------------------------.: Added a general anti-flood-protection to kad. If Kad receives more request of a specific type from one IP than it would expect, it starts ignoring those requests and envetually banning the source. This is supposed to avoid or slow down several attack scenarios..: Fixed a problem with injection of DNS servers into the routing tables which were able to stay because of a porotcol mixup between kad and dns. Old sources with port 53 as kad port are ignored, new clients (0.49a+) can use port 53 as kad port again but it is not recommended [found by netfinity].: Fixed a bug in kad2 with publishing >4GB files [netfinity]

------------------------ Jan, 11. 2008 ------------------------.: If you select a non-default incoming directory which already contains files, eMule notices you that those files are automatically shared by eMule

------------------------ Jan, 8. 2008 ------------------------.: Added a filter box (like in the search results) for on-the-fly filtering of shared files into the shared files tab. This filter is supposed to help finding specific shared files, it has no effect on which files are actually published.: Rearranged the symbols in the shared files directory tree a bit

------------------------ Dec, 15. 2007 ------------------------.: The onlinehelp for the options dialog is now topic sensitive for all languages instead only for english (well actually it is not, but this is serverside work which will be done step by step till the release). More areas to get topic sensitive to come in the future.: Open searches are now stored if you close eMule and restored on restart. This way you don't have to research your favourite words in case you didn't get to finish looking at the results. Can be disabled in Options->Display

------------------------ Dec, 2. 2007 ------------------------.: Reworked Kads Firewall handling and testing:The kad firewall state is now split into TCP and UDP. The TCP state is basically the old state, which tests if your TCP port is reachable. The UDP state is new and checks if your UDP port is reachable. For example on Full Cone NAT Routers, without portforwarding you will get TCP firewalled (as before) but UDP open (new). If you have the UDP open state, eMule doesn't needs a buddy any longer and will fully participate in the KAD network and therefore take away the overhead they caused in earlier versions (you still cannot connect to other TCP firewalled clients if you are TCP firewalled yourself)..: The new UDP state is shown in the MyInfo field in the Server Tab. As long as the UDP firewalltest is unfinished "(unverified)" is appended.: Clients which have the Kad UDP open state, now support direct callbacks (invoked by an UDP packet) to connect to not firewalled clients. These callbacks are faster, more reliable and use less ressources than buddy or server callbacks..: The new firewall test also fixes a bug / design flaw which caused eMule to always use the use the clients source UDP port, instead testing if the internal set UDP port might be the propper choice instead. This was especially a problem on Restricted Cone Routers with PAT (Port Address Translation)

------------------------ October, 31. 2007 ------------------------.: The messagesystem is now able to find your friends even if their IP changed if you and they are in Kad and not firewalled. This will help to stay in contact with friends longer than one session (Only works for new added/new seen friends which have Kad enabled)..: When messaging a friend, eMule now makes sure that the userhash still matches after connecting and SecureIdent (if enabled) is passed in order to ensure that its really your friend.

------------------------ October, 28. 2007 ------------------------.: You can now bootstrap to kad from an URL which points to a nodes.dat file (in the Kad tab)

------------------------ October, 22. 2007 ------------------------.: In order to reduce spam messages and by this make the messagesystem more useable again, eMule now supports Captcha authentification:If enabled, someone who messages you has first to solve a cpatcha (an image which shows letters) before the message is shown to you. Older clients who do not support captchas will be unable to message you and receive a notice about this.

------------------------ Jule, 11. 2007 ------------------------.: Added obfuscation to the Kad UDP protocol. Kad obfuscation is part of the protocol and is unrelated to the Ed2K-Obfuscation settings

------------------------ June, 5. 2007 ------------------------.: Fixed a bug which let Kad try to load its preferences from the old config directory location