SQLiteCrypt With Entity Developer

Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
Post Reply
caduetcorp
Posts: 1
Joined: Fri 14 Aug 2015 16:29

SQLiteCrypt With Entity Developer

Post by caduetcorp » Fri 14 Aug 2015 16:51

Hello there, we are new using the Entitydeveloper Product. we decided to migrate from Telerik Data Access and VistaDB to your framework (Which by the way we think is the best tool in the market for RAD).
Now, our problem resides that because we where using VistaDB, that system has built in encryption for the database. we have acquired the rights to use SQLiteCrypt, because we want it to include encription in our databases like we always have done with VistaDB but now that your framework does not support VistaDB we need to migrate all out future solutions to SQLite together with SQLiteCrypt.

We have looked through your forums help and documentation but there is not a clear tutorial or instructions in how really to use SQLiteCrypt with your product. You say you support it, even in the advanced properties tab of the connection you can place the license code and the password for the database. but the database the entitydeveloper framework creates even when we replaced the sqlite3.dll in the windows32 directory is not encrypted.

It will be nice for many users to have a small bullet point step by step list in how to use SQLiteCrypt with your product for example:

1) Replace the sqlite3.dll on C:\Windows\System32 with the SQLiteCrypt sqlite3.dll
2) On the connection wizzard go to the advanced page and place the database password and license information for the SQLiteCrypt component after choosing encryption method SQLiteCrypt
3)
4)
5)

Something like this will be nice, so people are able to understand how to use encryption using this SQLite module you support. We have been playing around and reading the information you have in the website which from the stand point of the entitydeveloper tool is not only missing but the information that is available about it it focuses on the Dotconnet SQLite product and is not really that helpful when it comes to setup the SQLiteCrypt component for use with the EntityDeveloper product.

So a small step by step guide from Devart´s side, will be great so we can start using AES256 protection in our embedded databases created with the EntityDeveloper framework.

Thank you and i look forward to your answer

Pinturiccio
Devart Team
Posts: 2192
Joined: Wed 02 Nov 2011 09:44

Re: SQLiteCrypt With Entity Developer

Post by Pinturiccio » Mon 17 Aug 2015 13:55

caduetcorp wrote:It will be nice for many users to have a small bullet point step by step list in how to use SQLiteCrypt with your product
Our documentation contains an article on SQLiteCrypt. For more information, please refer to https://www.devart.com/dotconnect/sqlit ... Crypt.html
caduetcorp wrote:We have been playing around and reading the information you have in the website which from the stand point of the entitydeveloper tool is not only missing but the information that is available about it it focuses on the Dotconnet SQLite product and is not really that helpful when it comes to setup the SQLiteCrypt component for use with the EntityDeveloper product.
You need to specify the corresponding connection string parameters described in the dotConnect for SQLite documentation, in order to use SQLiteCrypt in Entity Developer. After this you can work with an encrypted database in Entity Developer. However, if you want to do more advanced SQLiteCrypt-related actions than simply opening an SQLiteCrypt-encrypted database, you need to use dotConnect for SQLite.

For example, Entity Developer does not allow changing a password for an encrypted database or encrypting an unencrypted database; you need to use dotConnect for SQLite for this. You need to create a simple application that creates an SQLiteConnection instance, opens the connection to the database and calls the ChangePassword method for changing or setting the password. For more information, please refer to https://www.devart.com/dotconnect/sqlit ... Crypt.html
caduetcorp wrote:but the database the entitydeveloper framework creates even when we replaced the sqlite3.dll in the windows32 directory is not encrypted.
It can happen because of one of the following reasons:
1. A newly created empty database is not encrypted. SQLiteCrypt does not encrypt empty databases. It will become encrypted immediately after you, for example, add a table to it.
2. An sqlite3.dll library without the SQLiteCrypt extension is used. Make sure that your application uses the sqlite3.dll library with SQLiteCrypt.

Post Reply