Infralution Support

[Pointeman]

Q. Should the 'RegistryEvaluationMonitor' password match the the 'Product Password' used in 'License' Tracker?

EvaluationMonitor evalMonitor = new RegistryEvaluationMonitor("password");

[Infralution]

Definitely NOT. That would potentially allow someone to decompile your software and discover your Product Password which may allow them to generate keys. It should be ideally something which will be unique to your product to avoid the possibility (however small) of it clashing with another product from another developer.
_________________
Infralution Support

[Pointeman]

Okay, that makes sense to me.

Thanks again

[DBartlett]

I was just about to post the same question. So I assume that this password is obscured in the code, correct? Obviously it would be easily exposed, but as it only relates to the evaluation process, we can live with that. Could you provide any examples of obfuscation, or should I just roll my own scrambler? I'm really happy with the product by the way. Dale

[Infralution]

The password used is scrambled to produce the location used in the registry to to store the evaluation data. That means someone can't just examine the code and find the registry entry - but it is not that much more work to simply replicate the code and then debug into it to find the registry entries being used. This just gives someone the ability to extend the evaluation period - which is one reason why you want to limit the functionality of your product during evaluation. I would probably recommend using and encryptor (like Infralution .NET Encryptor) or an obfuscator to try and make this a little more difficult.
_________________
Infralution Support