[cod] forget about IW2 and get back to work :)

Tue Oct 20 10:05:28 EDT 2009

that's not true.
(pirated versions of 1.3 exists too afaik!)

we do give the users the possibility to install ANY version of ANY game that
has ever been released.
During the initial setup (or whenever they want to reinstall the gameserver)
the wizard ask them which specifc version they want...

we do support 1.0 version because someone still want it due to a specific
reason:
that's the version that works out of the box... and many "noobs" that just
wants to enjoy gaming do not have any idea about updates and such... they
just put the cd into the computer... install the game... and go online
playing...
in that scenario they are able to play only con cod1.0 servers...

(additionally 1.0 do not have punkbuster support..... before pointing the
finger to possible pirates I think more about cheaters ;) )

On Tue, Oct 20, 2009 at 12:44 PM, Steven Hartland
<killing at multiplay.co.uk>wrote:

> Ermm no one rents 1.0 here as that's just saying your support pirates.
>
>   Regards
>   Steve
> ----- Original Message ----- From: "pet" <games at maxrate.pl>
> To: "Call of Duty server admin list." <cod at icculus.org>
> Sent: Tuesday, October 20, 2009 11:18 AM
>
> Subject: Re: [cod] forget about IW2 and get back to work :)
>
>
>  Sorry, wrong thinking. lam not going to remove  cod2 1.0 server from my
>> offer, it would be a suicide  like for other game hosting companies in my
>> country. Nearly 80% call of duty customers rents cod2 1.0 version. Above
>> mentioned problems doesn't appear each day, but one time per month. Our cod2
>> 1.0 community is very large. They do not play 1.0 because of pirated
>> clients, they do this because the 1.3 patch brings many unexpected
>> add-ons/patches which makes the game-play very poor. The same issue was by
>> counter strike 1.4, the aiming was beautiful and game was nearly perfect,
>> there was no need to make some improvements, but unfortunately the new 1.6
>> patch made this game unplayable. If somebody is cheating on cod2 1.0 he can
>> also cheat in further versions as well, cheaters are everywhere, it's up to
>> You how to handle with them. Naturally cod2 1.3 is very good for clan
>> battles etc., You have more tools to fight with the cheaters and pirated
>> clients and this is a good site of this version and  punk buster
>> implementation  as well. There are always good and bad sites. But as I
>> mentioned before, I will not resign from cod2 1.0 or counter strike 1.4 as
>> long as theirs communities still growing  up and there will bo more fans
>> than any other FPS game on our market. Do not forget, we have a here some
>> phenomenon,  how old this game is - we know it,  how much servers  are still
>> on-line - we know it. There will be a lots of games which dies with natural
>>  death, but cod2 1.0 will be still alive :). For me it means more than
>> game...
>> Bong-Master pisze:
>>
>>>
>>> Tell your customers to update there game as you are updating the servers
>>> :P Nice simple solution. pirated clients use 1.0. Pet Do the good thing say
>>> Bye Bye  to you 1.0 Clients & support the game in the way this mailing list
>>> dose. You personally are letting the side down so to speak Simply by
>>> allowing pirated clients to use your services. But then in a diffrent way
>>> who do you blame the client or the hoster ?? My personal view is that i
>>> blame the hoster First then the client Simply because if the hosted DID not
>>> offer this service the client would not have a dedi server to play his
>>> pirated game on.
>>> --------------------------------------------------
>>> From: "pet" <games at maxrate.pl>
>>> Sent: Tuesday, October 20, 2009 8:29 AM
>>> To: "Call of Duty server admin list." <cod at icculus.org>
>>> Subject: Re: [cod] forget about IW2 and get back to work :)
>>>
>>>  I have to find some solution, most of my customers order 1.0 version, is
>>>> very popular.
>>>>
>>>>
>>>> escapedturkey pisze:
>>>>
>>>>> People run 1.0 to support pirated clients. Is this not true? If so,
>>>>> well, our supporting and helping them gives IW justification for dumping
>>>>> dedicated server support.
>>>>>
>>>>> pet wrote:
>>>>>
>>>>>> So :) I have some little problem, which is probably well known:
>>>>>>
>>>>>> ERROR: Attempted to overrun string in call to va()
>>>>>>
>>>>>> yep, somebody has messed up on my cod 2 1.0 server
>>>>>>
>>>>>>
>>>>>>
>>>>>> "va() is a function of the Quake 3 engine used to quickly build
>>>>>> strings
>>>>>> using snprintf and a static destination buffer.
>>>>>> Read more on: : i3D.net Game Forums
>>>>>> http://forum.i3d.net/call-duty-series-newsletter/48158-cod-cod-ww-1024-bytes-command-exploit.html
>>>>>> If the generated string is longer than the available buffer the server
>>>>>> shows an "Attempted to overrun string in call to va()" error and
>>>>>> terminates.
>>>>>>  From Call of Duty 2 (and consequently) the size of this buffer has
>>>>>> been reduced from the original 32000 bytes to only 1024 causing many
>>>>>> problems to the admins.
>>>>>>
>>>>>> So in CoD5 an attacker which has joined the server can exploit this
>>>>>> vulnerability through the sending of a command longer than 1024 bytes
>>>>>> causing the immediate termination of the server."
>>>>>>
>>>>>> I try it, and it works. I you send this command to the server, it will
>>>>>> crash:
>>>>>>
>>>>>> cmd aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>>>>>> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaa
>>>>>>
>>>>>>
>>>>>> so
>>>>>>
>>>>>> any solution ?
>>>>>>
>>>>>>
>>>>>> any help will be appreciated.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cod mailing list
>>>>>> cod at icculus.org
>>>>>> http://icculus.org/mailman/listinfo/cod
>>>>>>
>>>>>>  _______________________________________________
>>>>> cod mailing list
>>>>> cod at icculus.org
>>>>> http://icculus.org/mailman/listinfo/cod
>>>>>
>>>>>
>>>> _______________________________________________
>>>> cod mailing list
>>>> cod at icculus.org
>>>> http://icculus.org/mailman/listinfo/cod
>>>>
>>>
>>> _______________________________________________
>>> cod mailing list
>>> cod at icculus.org
>>> http://icculus.org/mailman/listinfo/cod
>>>
>>>
>> _______________________________________________
>> cod mailing list
>> cod at icculus.org
>> http://icculus.org/mailman/listinfo/cod
>>
>>
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd. and the
> person or entity to whom it is addressed. In the event of misdirection, the
> recipient is prohibited from using, copying, printing or otherwise
> disseminating it or any information contained in it.
> In the event of misdirection, illegible or incomplete transmission please
> telephone +44 845 868 1337
> or return the E.mail to postmaster at multiplay.co.uk.
>
>
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20091020/c6430ba2/attachment-0001.htm>