View previous topic :: View next topic |
Author |
Message |
Pointeman
Joined: 07 Sep 2010 Posts: 56
|
Posted: Wed Dec 29, 2010 4:20 pm Post subject: RegistryEvaluationMonitor Password? |
|
|
Q. Should the 'RegistryEvaluationMonitor' password match the the 'Product Password' used in 'License' Tracker?
EvaluationMonitor evalMonitor = new RegistryEvaluationMonitor("password"); |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Wed Dec 29, 2010 11:17 pm Post subject: |
|
|
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 |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
Pointeman
Joined: 07 Sep 2010 Posts: 56
|
Posted: Thu Dec 30, 2010 1:39 pm Post subject: |
|
|
Okay, that makes sense to me.
Thanks again ![Smile](images/smiles/icon_smile.gif) |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
DBartlett
Joined: 16 Sep 2019 Posts: 14 Location: Uki, NSW, Australia
|
Posted: Mon Nov 18, 2019 5:03 am Post subject: RegistryEvaluationMonitor Password? |
|
|
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 |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Mon Nov 18, 2019 6:34 am Post subject: |
|
|
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 |
|
Back to top |
|
![](templates/subSilver/images/spacer.gif) |
|