![]() After that, the client application works with Firebird as usual. ![]() The code to initialize an encrypted connection is very simple – before the usual connection, several calls should be done to send an appropriate key. There are also examples for Lazarus, .NET, and PHP. The example of such an application is included in the CryptTest.zip archive with the demo plugin – there is a compiled version and full sources for it on Delphi XE8. Without nf, the encryption plugin will require receiving the key from the connected application. To imitate such an environment, we need to remove (or simply rename) the file with keys (nf) from the folder plugins. Step 2: Connect to the encrypted database with the client application If you want to connect to an encrypted database with your developer tools first - please read Step 3 below.Īfter the initial encryption, we suppose that the database will be copied to the customer environment, where access to it will be done only through the authorized application. Plugins/nf (for initial encryption in development mode)įnf (contains parameter to set encryption plugin) On the client's side (demo - CryptTest.exe) - 32bit In the table below you can see files we have on the server to enable the encryption, and what we need on the client-side: On the server's side (Firebird-3.0-0_圆4) Please note - on Linux it is necessary to use quotes and case-sensitive plugin and key names:Īlter database encrypt with "DbCrypt" key Red Īfter that, the database is encrypted with server-side authentication: the keys are located in the file nf. SQL> alter database encrypt with dbcrypt key red ĭatabase: localhost:C:\Temp\EMPLOYEE30\EMPLOYEE30.FDB Connect to the unencrypted database with isql and encrypt the database: isql localhost:C:\Temp\EMPLOYEE30\EMPLOYEE30.FDB -user SYSDBA -pass masterkey
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |