Firebird File and Metadata Security Geoff Worboys Version 0.6, 30 June 2020 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . connecting to the database require direct access to the database file itself. All access goes through the server process, which accesses the database file as needed to fulfil requests. It is the server that restricts restricts or allows access to the logged-in user, according to the permissions defined for that user in that database.  The “embedded” variation of Firebird server works differently and would not be

the database file; XNET (Windows only) requires username and password. 2. (only after backing up all your databases) Install Firebird 5 (see later sections) 3. Note down the permissions, ownership and this would require the security database to exist, and it would lock the file). 6. Change filesystem access rights/permissions to match the original security5.fdb For a Firebird 4 security database, There is a single, common database page cache. The server requires exclusive access to each database file it opens (hence the Dedicated). Each mode is fully stable and there is no reason to categorically

database file. Local connections On Windows, both architectures now support safe and reliable local connec- tions, with only the server process requiring access rights to the database file. Multiprocessor the process between CPUs. To prevent this, set the CpuAffinityMask parameter in the configuration file firebird.conf. Guardian When run as a Windows application (as opposed to a service) you can't use different on other Unix-like systems. Table 2. Firebird 2 component locations on Linux Component File Name Default Location Installation directory (referred to hereafter as ) — /opt/firebird

session; directly from the command line; and as a non-interactive session, using a shell script or batch file. Different tasks may be performed in each of the modes, as illustrated below: • An interactive session drop data or metadata. ◦ Input a script file containing a batch of SQL statements in sequence without prompting. ◦ Add and modify data. ◦ Grant user permissions. ◦ Perform database administrative functions to the operating system. • In a non-interactive session, the user employs a shell script or batch file to perform database functions.  Because other applications in the Linux environment, for example

Firebird Password File Utility Norman Dunbar Version 1.5, 18 June 2020 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . password. This is because those operating systems allow the system administrator to set file system permissions which prevent execution of certain programs and utilities for security reasons. The Firebird security.fdb for Firebird 1.5 or security2.fdb for Firebird 2.0 onwards. The default locations for this file are: • C:\Program Files\Firebird\Firebird_1_5 for Windows (Change '1_5' to suit your Firebird version)

switches the process between CPUs. To prevent this, set the CPU_AFFINITY parameter in the configuration file ibconfig. As you can see, neither of the architectures is better in all respects. This is hardly removed in Firebird 1.5. Table 2. Components of the Firebird 1.0 installation Platform Component File Name Default Location 32-bit and 64-bit Win- dows (Windows 95, 98, ME, NT, 2000, XP, ...) Installation System dir- ectory (see note below table) Firebird 1.0 Quick Start Guide 5 Platform Component File Name Default Location Linux and possibly other UNIX distros Installation directory (referred to

error -231 335544488 logh_small Log file header of %s too small -232 335544489 logh_inv_version Invalid version of log file %s -233 335544490 logh_open_flag Log file %s not latest in the chain but open set -234 335544491 logh_open_flag2 Log file %s not closed properly; database recovery may be required -235 335544492 logh_diff_dbname Database name in the log file %s is different -236 335544493 logf_unexpected_eof log file %s at offset %ld -237 335544494 logr_incomplete Incomplete log record at offset %ld in log file %s -238 335544495 logr_header_small Log record header too small at offset %ld in log file %s

. . . . . . . . . . . . . . . . . . . . . . . . 21 6.9. Create a Database Clone Without a Dump File.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.10. Backup 7.4. Gbak log file Cannot Be Overwritten . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.5. Use of 'stdin' or 'stdout' File Names . . . . -FE[TCH_PASSWORD] file name> | stdin | /dev/tty This switch causes the password for the appropriate user to be read from a file as opposed to being specified on the command line. The file name supplied is

error -231 335544488 logh_small Log file header of @1 too small -232 335544489 logh_inv_version Invalid version of log file @1 -233 335544490 logh_open_flag Log file @1 not latest in the chain but open set -234 335544491 logh_open_flag2 Log file @1 not closed properly; database recovery may be required -235 335544492 logh_diff_dbname Database name in the log file @1 is different -236 335544493 logf_unexpected_eof of log file @1 at offset @2 -237 335544494 logr_incomplete Incomplete log record at offset @1 in log file @2 -238 335544495 logr_header_small Log record header too small at offset @1 in log file @2 -239