> Hello Team Support, > > > I installed on a client machine, the ERP.FDB file and the application. > Now, I came to know that, one guy in the client place, stole > the ERP.FDB and tried several passwords and did not get it, so, he > installed a FIREBIRD on his computer and copied the ERP.FDB and opened > it with FIREBIRD default password, and stole the entire db design. > > How to protect from this kind of things ? > How to make sure, that the database cannot be copied?
Additional to the other comments. Firebird 3 will have support for optionally login credentials being embedded in the regular database and IIRC optional data and/or over-the-wire encryption. But V3 is in Alpha stage and not recommended for production usage. Although being far away from bullet-proof, but you could at least lock out SYSDBA from logging in by creating an equally named role, but then SYSDBA must not be an owner of the database and any database object (table, view etc.). Not bullet-proof, because knowledgeable people could open the database in a HEX editor and change the role name. But I found that as a first countermeasure quite ok in the past, especially when customers have initially no idea about Firebird, but then rather quickly found out the SYSDBA/masterkey combination via Google. -- With regards, Thomas Steinmaurer http://www.upscene.com/ Professional Tools and Services for Firebird FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
