solraccheffy
asked on
a "vairable"
I am building something taht a client has paid for a specific amount of license for, so in our code we have a number represnting that...but if they purchase more license we need to update taht number.
Is there a better way of doing this other than resend the client another DLL?
Please adivse of another way, but it needs to be secure and in a way so the client wont figure it out so they wont increase the license number.
Please advise.
Is there a better way of doing this other than resend the client another DLL?
Please adivse of another way, but it needs to be secure and in a way so the client wont figure it out so they wont increase the license number.
Please advise.
Callandor
You could construct a key that incorporates the number of licenses allowed, then have the program read the key and calculate how many licenses that key represents. The encryption algorithm to create the key needs to be sophisticated enough (perhaps involving large prime numbers) to prevent breaking and will only allow the program to work if a valid key is provided.
ASKER
That is kind of what I am looking for....I have that thought but not sure on how to go about implementing it.
please advise.
please advise.
Have you taken a look at how PGP is implemented? There is a public key and a private key, and though you don't need a public and private key, you could code the public key to decrypt what you send that's encrypted with the private key. This could include how many licenses, and the program could reject any answer outside a range. The client would only see an encrypted license key, which the program would decrypt and figure out how many licenses they have. They would not be able to change the license key without knowing what the private key was.
ASKER
Makes sense, where can I get an example on how to do this, step by step?
Take a look at http://www.pgpi.org/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the bad thing about the sample solution is if they trace the dll and find the
strMDAppend , then you are screwed :-( but if they can trace the binary
code, I guess they can do everything.
strMDAppend , then you are screwed :-( but if they can trace the binary
code, I guess they can do everything.