Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: phranque
The basic issue is that we are eventually going to have affiliates who can refer traffic for revenue share.
The way it works is that when a user (who is referred by an affiliate) downloads the client, the server puts the affiliate ID into the game launcher (setup.exe).
So when a user then installs the client and then registers to become player, the client uses affiliate ID for the registration step (ie to ensure that the affiliate gets the credit for the referral).
Therefore, the server changes (or patches) the game launcher (setup.exe) with an affiliate ID.
My coder has told me that because of this we cannot sign the launcher because each time it is patched the certificate will become invalid.
Have any of you had this problem? Is this correct? If so, is there a way we can get around this problem?
Your only option is to sign one copy for each affiliate. When a new version is released, you'll either have to delete all the signed copies and arrange for new signed copies to be created on demand or you'll have to create a new set of signed copies.
The signing process is very quick unless you need to include a timestamp (recommended). In this case it may take a few seconds to connect to a timestamp server.
I would recommend creating new signed copies on demand if you running on a Windows server, but if you are running on something else this might be tricky.