Answer the question
In order to leave comments, you need to log in
How to generate a crypto key or something to identify the client?
Task - I have a dll library that is installed on the client and does something useful there, it goes to my server for updated content. How to make it uniquely identify this library at the moment when it comes for updates, in other words, so that each client has its own unique copy of this dll. Updates cost money, so it needs to be difficult (impossible) for a client to modify a library to, for example, pretend to be another client's library and receive updates for another. How to solve the problem, in the direction of which technologies to look?
Answer the question
In order to leave comments, you need to log in
Wouldn't it be easier to store information that a client with such a unique ID has already received an update, and not reissue an update to him. Then the user who "shared" his distribution, dug a hole for himself.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question