22 wrote:
Sure, we are calling it FlightData Upload Manager, every ppl registered to competition must use this for briefing access and than for FTR,IGC upload. It solves using extra soft which we need. Than there are a few ways how find doublers, e.g. we can identify some PC components, we can read registry and compare with some DB. I think its enough. Simple warning system, which identify users with strange behaviour or similar hardware/registry config.
Clever

For security reason, don't send the registry key generated from serial number, but a hash of it instead!
Or better, don't use it at all and use other (secret) registry key, cheetah could temporary change the Condor registry key in order to obtain another ID.
I've another idea for your tool:
It could generate a code valids for 24h, like <UNIQUE ID>.<PILOT ID>.<CODE_OF_THE_DAY>.<CRC>
Unique ID = generated from Condor installation
Pilot ID = according to the pilot used in Condor menu
Then, me and others could use your system too on their site. Each time the guy wishes to upload a FTR, we could ask for this code and check the CRC.
And, thanks to the temporary code, it's more difficult to get differents codes if the user tries to cheat!
Thierry