Re: [QStat-devx] Heads up new GameSpy protocol

[Ludwig N. <l-...@us...>]

Steven Hartland wrote:
> >>As such I hope to spend some time over the weekend
> >>to add this in and hopefully GameSpy will be providing me
> >>with a server I can test against in the near future.
> >
> >Could you do it a branch or delay checking it into cvs until its
> >tested and sufficiently stable? I'd like to release qstat ASAP after
> >Quake4 comes out and would prefer if qstat wasn't broken at that
> >time. We can do another release if the first game that uses the new
> >gamespy protocol shows up.
>
> BF2 will be moving to this very shortly so I want to get it in.
> ATM DDoS attacks are causing everyone significant pain
> which was the driving factor for me getting GameSpy to fix
> this issue in the first place. The core protocol hasnt changed
> its just the addition of a challenge response phase to the
> beginning. As such I'll just be adding a -gs4 which will extend
> the code in gs3 to support this additional C/R.

So you basically don't need to touch qstat.c, good :-)

> >>I just thought you guys should be aware that we have
> >>this information and I now a good contact in GameSpy
> >>who seems to be willing to help us out if he can.
> >
> >That's cool. Would it be possible to carefully ask that guy about
> >the master server? Would be nice if I finally had out of the box
> >support for that in xqf.
>
> What sort of thing are you looking for there?

The master requires authentication. Every game has it's own key.
The authentication algorithm has been reverse engineered and the
keys are public acessible on the gamespy web server. Nevertheless it
would be good to have either official documentation how it works or
a statement that it's not illegal to use the reversed stuff to
access the gamespy master. I don't want to get sued by gamespy inc.

cu
Ludwig

-- 
(o_  Lud...@we...
//\
V_/_ PGP Key ID: FF8135CE