It is necessary to protect the data used and generated by the program in the process. There is an idea to use a password-protected SQLite database. This will protect the data from modification, but there remains the possibility of replacing the database file itself with an earlier version (for example, the software that was previously copied after installation). Alternatively, you can maintain the versioning of the database file and register the key with the latest version of the database file in the registry. But this is not a panacea, when you run the program, you can track changes in the registry, and then roll back the database file and key value. Need advice on how to protect data? What are the practices?
- If this corporation is a computer in the domain, you can check the time. The same time can be checked through the Internet. - nick_n_a
- oneAs long as the data is stored where the user has access, he can always replace them. The only difference is how much he will have to be confused for this. - Regent
- It is not necessary to prevent data substitution, it is enough to detect it. - RusGIS
- You can add a file with the "signature" of the database, which is salted, is constantly updated when the program is running, in case of not working within n-days it becomes "expired" Then after n-days they will not be able to replace it. You can ... n make variables (longer holiday times). - nick_n_a
- oneI’m not catching something, I guess, but if your database is encrypted, then what might be the reason for changing the base file with the previous version? Then the entered data will be lost from the beginning of using the program. And why do we need entries in the Windows registry; if you have a database, write everything you need there. The program comes with a zero base and requires register.key. You sell the key to the user, the key is then encrypted and written to the database. The program starts and checks for the presence of a key in the database, if there is no such key in the database means ... - Bulson
|