after backing up all your databases) Install Firebird 5 (see later sections) 3. Note down the permissions, ownership and filesystem access rights of security5.fdb 4. Rename the existing security5.fdb 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, it is also possible to FIRSTNAME 'firstname' | MIDDLENAME 'middlename' | LASTNAME 'lastname' | {GRANT | REVOKE} ADMIN ROLE | {ACTIVE | INACTIVE} | USING PLUGIN plugin_name ::= tag_name = 'tag_value'

a batch of SQL statements in sequence without prompting. ◦ Add and modify data. ◦ Grant user permissions. ◦ Perform database administrative functions. • Directly from the command line, with individual do not show the message "Use CONNECT..." -r(ole) <role> role name -r2 <role> role (uses quoted identifier) -s(qldialect) SQL dialect (set command line isql options. _Using -r2 and -r(ole) This switch can be used to specify a case-sensitive role name. The default switch for this is -r(ole). Roles provided in the command line are uppercased.

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 will also result in a prompt for the password.  Firebird 2.5 onwards. -role role name> Allows the specification of the role to be used by the connecting user. -database -fetch_password -role role name> -trusted (use trusted authentication) -database

for %s access to %s %s -551 335544790 insufficient_svc_privileges Service %s requires SYSDBA permissions.Reattach to the Service Manager using the SYSDBA account. Firebird 2.0 Error Codes SQLCODE GDSCODE gsec_db_admin_pw_specified Database administrator password already specified -901 336724049 gsec_sql_role_specified SQL role name already specified -901 335741012 gfix_unexp_eoi Unexpected end of input -901 335544407 -901 336330940 gbak_missing_username User name parameter missing -901 336068796 dyn_role_does_not_exist SQL role %s does not exist -901 336330941 gbak_missing_password Password parameter missing -901

for @1 access to @2 @3 -551 335544790 insufficient_svc_privileges Service @1 requires SYSDBA permissions.Reattach to the Service Manager using the SYSDBA account. -552 335544550 not_rel_owner Only the gsec_db_admin_pw_specified Database administrator password already specified -901 336724049 gsec_sql_role_specified SQL role name already specified -901 335741012 gfix_unexp_eoi Unexpected end of input -901 335544407 d A blocking factor may not be used in conjunction with device CT -901 336068796 dyn_role_does_not_exist SQL role @1 does not exist -901 336330940 gbak_missing_username User name parameter missing -901

ISC_PASSWORD environment variable exists and has the correct value. -RO[LE] role name> Allows the specification of the role to be used by the connecting user. Not of much practical use and is not normally -REP[LACE_DATABASE] replace database from backup file -RO[LE] Firebird SQL role -SE[RVICE] use services manager -T[RANSPORTABLE] transportable backup metadata only -PAS(SWORD) Firebird password -RO(LE) Firebird SQL role -SE(RVICE) use services manager -USER Firebird user name

requests. It is the server that 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 does not have access anyway. Some have reported limited success in this respect by creating an SQL role name of SYSDBA and making sure it does not have access to the database objects. However it does (no password authentication occurs) is used to manage user access to database objects (via SQL permissions) but if that user name is SYSDBA (or the owner of the database) then unrestricted access is possible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 8.12.4. RDB$ROLE_IN_USE() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 11.3. CURRENT_ROLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 13.1.2. RDB$ADMIN Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.15. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.15.1. CREATE ROLE. . . . 180 5.15.2. ALTER ROLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 5.15.3. DROP ROLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 9.3. CURRENT_ROLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .