Bernd <be...@web.de> wrote: > This may not be really SQLite specific, but as it's at least SQLite > related I thought I asked here. > Our program ships with an encrypted SQLite database that has to be > opened by the application to process some other data. As it's a .NET > application, it's very easy to peek inside the source code (even though > I'm planning to use an obfuscater tool). Are there any best practices on > how to store the password to open the database?
Generate a random password when first creating the database. Encrypt it using ProtectedData.Protect and store the encrypted version somewhere (e.g in the registry, or in a file alongside the database file). Decrypt with ProtectedData.Unprotect before using. This effectively encrypts the password with the user's Windows login credentials. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
