Security?

I believe that even most of the data stored in the database is encrypted. I think what would work here (and I have suggested) is an offline expiration policy. That way if the computer is lost\stolen the offline mode would expire and become unusable unless they could connect to the SQL server again. He has agree'd to add the expiration policy but I am not sure when.

To protect the data in the database, it helps to not save the SQL Server password in the data source, so the user has to enter it every time.
The problem is Offline mode. If I can open the database without even entering a password, its not safe really.

IMO all locally stored data (including data source configuration, which includes a password, too) should be encrypted using a key entered by the user, which he must enter every time the program is launched.
By encrypting the data source configuration, the SQL server password is safe, too. and each user can have their own key.

That would be nice to have for other reasons, but it doesn't add much regarding security

Ultimately, we should force users to encrypt their whole hard drives.

Hi,
I'm not sure if I will have the time to add this for this release, but I take every security problem seriously and I will add the option to ask for a password for the offline mode. The encrypted data will use a mix of the machine info, our private key and the password.

As I'm testing I see this as a huge issue preventing use of the program in the way I would most likely deploy it. In addition to the complete lack of security for offline mode, Locking the datasource doesn't stop you from hitting duplicate or viewing the settings, which renders that useless. So I would have to disable offline mode for everyone.

Hi,
I understand your concern and this is why we plan to add more security features.