Ghostship from WmW wrote:Whilst doing my usual monitoring of the network yesterday amid increasing reports of folks dropping from rooms, I noticed that once again the familiar 1.x.x.x pattern associated with KM's WCS bug, it seemed to go from being present 50% of the time to in one period almost outnumbering ordinary traffic by 20 to one, a level sure to cause random room dropping, cache disruptions and affecting other aspect of the WPN that are more obscure.
The problem that springs to mind is that this activity can fall into three possible scenarios,
1 - KM can control the effect and uses it to cause disruption when he feelks like it.
2 - WCS users are still using out of date Versions with the flaw.
3 - Third party attackers are duplicating the method to cause general network disruption.
To negate points one and two I had asked folks to hold off of using WCS but it seems my request fell on deaf ears, so I now call upon KM to look up which of his users are using the Buggy WCS version and get them to upgrade, only by this action will we be able to ascertain the correct scenario and therefore be able to take the correct remedial action to deal with this problem, please take note folks burying our heads in the sand wont fix this.
For those of you with short memories, KM's little chat creation WCS had what KM decribed as a "typo" this "typo" caused a number of issues, including people droping from channels and channel listing issues. This "typo" took KM weeks and weeks to fix, which leads me to suspect his disruption of the network was intentional.
My advice to all Winmx chat users is GET RID OF WCS and use something else, Ouka is a stable and well featured option.
You can get Ouka here http://ouka.dip.jp/archive/ChatServerE_ ... 8_0000.zip
Comon folks, spread the word, lets get KMware off the winmx network!!!
SitemapIndex
RSS Feed