Gizmo [EMAIL PROTECTED] wrote:
I have a similar situation in one of my applications. The
customer wishes to secure the database. Since we use a Btrieve
database, the only way to do
this is be setting an owner name on the DB, and then
encrypting using the owner name as the password.
Chris,
Your situation is a little unique in that you encrypt the data with the
password. The data backend I was referring to is simply a backend database
like an SQL Server, Oracle 8i or DB2 data repository. All users need to do
to get access to it is to authenticate to it and then have the
If you are just talking about a password to access a db, the 'typical'
approach (at least the approach I use) is just to store that password
in the code/config file. You may like to add a layer to that by
encrypting it in some config file, and requiring a 'decryption'
(initialisation) of the
The Pervasive.SQL database has two access modes: native Btrieve and SQL.
The native Btrieve mode has as it's major advantage that it is about 10
times faster than MSSQL on the same hardware. However, it is NOT SQL; it is
a transactional database engine designed for applications that need a small
I'm wondering whether role-based credentials, vs. individual user
credentials, might not make more sense here. Could the database owner
key be issued to a role vs. an individual identity? In this way, your
human users could be associated with a role that has a right to issue a
query to the
