jeudi 21 mai 2015

Different Encryption password for every deployment of a SQLite Database with System.Data.SQLite

I'm currently trying to develop a locally restricted database application using WinForms, C# and Visual Studio 2013. My project lead stopped any usage of SQL Server Compact due to the unclear status of future development. I am now currently assessing whether SQLite with System.Data.SQLite as a toolkit with Entity Framework as a mapper can do the job as well. I am tripping over a requirement that every embedded database file has to be encrypted with a password. The Visual Studio tools give me the option to encrypt/set a password at creation time of the SQLite-File.

The problem is that every deployment has to have a custom password (and probably user) which in turn should probably be accessible through some sort of file/database (maybe an internal DB table on our end where user + PW for the databases are stored), so that non-Devs can add new possible deployments as well. Alternatively any form of user-management (and in turn user login capabilities) would work as well. Google is just not helpful in this regard.

Please note that, yes, I could custom-code a crazy spaghetti solution for most of this stuff if I really wanted, but this application has to be both maintainable and should not deviate too hard from established solutions.

So to summarize the question: Are there any available mechanisms for managing deployment of encrypted SQLite-Files to multiple users or any user-management functionalities I should take a look at?

Aucun commentaire:

Enregistrer un commentaire