DataSet memory Container
My problem today.
I developed a system that is going to be sold to many clients. The problem with firebird nowadays is that anyone can copy the database file and open it in its computer. Using SYSDBA and masterkey the database file can be opened in any computer and then, all your register can be copied.
My dream would be that the user and password could be into the database file and not in the server. But I think this is so far away to come true.
Then, I see a possibility to have all my strings rows encrypted, but I need to use some commands from sql, mainly the “like” command.
It should be a good idea to have a dataset container, where all the rows from a table can be copy and descripty in memory and IBCQuery can connect on it and it have all the sql commands.
What do you think about?
thanks
-
Anonymous commented
To help secure Interbase, or Firebird, 1st is to change SYSDBA password to something different. Second the client only needs to be able to see where the Server is executing. To secure a DB properly the end client does not need to see or have any access to the DB file. The DB engine of Interbase, or Firebird needs to be able to have full access to the DB file itself.