On the defense of piracy enablers
Posted Aug 24, 2005 8:59 UTC (Wed) by jzbiciak
(✭ supporter ✭
In reply to: On the defense of piracy enablers
Parent article: On the defense of piracy enablers
I can think of at least one way for it to work with the pass-through method. Since all the CD Keys are unique, require all copies to play on the Blizzard server network at least once.
When the CD key's registered, issue that client a public key and Blizzard keeps the private key. Whenever a client connects to a 3rd party server, pass the CD-Key through to Blizzard. After Blizzard checks that the key's unique and not being played by more than one machine, they then send back a date code signed by the private key. The 3rd party server needs to send this back to the client before the client agrees to trust the server.
All this assumes the client and the Blizzard servers are not modified and the only thing non-original is the 3rd party server. So, every so often the client makes a request for Blizzard server auth, and if it doesn't reply with an appropriately signed date code within an appropriate time frame, it disconnects. It's that simple. The 3rd party server only needs to pass through these requests to Blizzard. And Blizzard can choose whether to preemptively send signed date codes down to the 3rd party server to prevent disconnects due to network instability.
So, yeah, you could do #3 and do it in a way that can't be circumvented by "return TRUE;"
to post comments)