But the server method makes so much more of a mess and takes more effort. Also, it doesn't give us the same security we'd have with the key.
Also, wtf happened to your screen name?
(still @limited): Whereas my method would involve having one of our own servers wait for someone to join with a certain name and enter a short (random) code.
Either way, we're looking to link a Modacity account (and therefore a Cerebrum account) with a CD key in a way that can't be spoofed, yes. The idea with jcap's method is that we display the hash to the user, but the key should still be the thing that is sent - or at least, that's what I hope, as I can easily change the contents of a disabled text field...
Yeah, I want to show the hash to the user to give people the peace of mind that we're actually using what it generates, not the actual key. You're right, we might need to send the actual key and then calculate it on the server anyway because it's too easy to edit the field or edit the HTTP data. I did think of that, but I only mentioned it to Kornman and ShadowSpartan, I think. We'll just need to make it clear in the Terms of Service that the key is used solely for generating the hash - nothing else - and that the key is purged immediately after the hash is created.
Either way, we would still need to know how the hash is generated, whether it's done by javascript or PHP.
@kornman00: This is the format I'd like to have the Yelo dump come in. If you need to remove anything or feel that you can add anything, let me know, as this is what I'm building my 'lite' game viewer off of. The reason for keeping various parts is that I want the format to be as close to the final as possible (hence "overallMetrics" being alone in the <players> block)
Now is the when you should start saying "hey, that actually is starting to look like a game viewer". Style and formatting time!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks