In that case, connect to localhost:path-or-alias or specify a protocol like xnet:// (Windows only) or inet://. This may fail if your OS login doesn’t have sufficient access rights to the database file. If the connection string doesn’t start with a host or protocol name, a direct serverless connection to the database is attempted. If you hit Enter after your statement and you’ve forgotten the semicolon, just type it after the CON> prompt on the next line and press Enter again. This enables you to split long statements over multiple lines. If you hit Enter and the line doesn’t end with a semicolon, isql assumes that the statement continues on the next line and the prompt will change from SQL> to CON>. In isql, every SQL statement must end with a semicolon. Protect databases on the filesystem levelĪnybody who has filesystem-level read access to a database file can copy it, install it on a system under his or her own control, and extract all data from it - including possibly sensitive information.Īnybody who has filesystem-level write access to a database file can corrupt it or totally destroy it. You can do this with the SQL user management commands as shown above, or with any decent third-party Firebird administration tool. Instead, generate normal user accounts, and provide their account names and passwords to your users as needed. Therefore, you shouldn’t use this super-account to create and populate regular databases. Its password should be known to a few trusted database administrators only. SYSDBA is a very powerful account, with full (destructive) access rights to all your Firebird databases. Change SYSDBA's passwordĪs discussed before, if your Firebird server is reachable from the network and the system password is masterkey, change it. The default practice - running the service as the LocalSystem user - poses a security risk if your system is connected to the Internet.Ĭonsult in the doc subdir to learn more about this. On Windows server platforms, you can also run the Firebird service under a designated user account (e.g. On Unix-like systems, Firebird already runs as user firebird by default, not as root. $(install)\WOW64 (with an optional copy in SysWOW64 - see second note below table) $(install) (with an optional copy in - see note below table)ģ2-bit library versions for use with 64-bit Firebird Isql.exe, gbak.exe, nbackup.exe, gfix.exe, gstat.exe, etc.Įngine12.dll, srp.dll, udr_engine.dll, etc.įbclient.dll (with an optional gds32.dll, to support legacy apps) Firebird 3.0 component locations on Windows Component Likewise, refers to the Windows system directory.īe sure to read the notes below the table, especially if you’re running Firebird on a 64-bit Windows system. This is usually “ C:\Program Files” but may also be a different path, e.g. In the table below, refers to the Windows programs folder. (actually, the real stuff is in $(install)/lib, but you should use the links in /usr/lib) Legacy libgds.* symlinks are also installed. The usual symlinks ( *.so.2, *.so) are created. LibEngine12.so, libSrp.so, libudr_engine.so, etc. opt/firebird (may vary per distribution) Installation directory (referred to hereafter as $(install)) Firebird 3.0 component locations on Linux Component Some of the locations may be different on other Unix-like systems, or on certain Linux distributions. The following table shows the default component locations of a Firebird installation on Linux. Allowing users to log in during a restore Creating a database as a non-privileged user Making sure that the Firebird server is running Installing on Linux and other Unix-like platforms
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |