. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Gsec Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6. Running Gsec Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Gsec caveats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table of Contents 1 Chapter 1. Introduction Gsec is the security database manipulation utility. It allows the SYSDBA (or any privileged user) the

336723983 gsec_cant_open_db Unable to open database -901 336723984 gsec_switches_error Error in switch specifications -901 336723985 gsec_no_op_spec No operation specified -901 336723986 gsec_no_usr_name specified -901 336723987 gsec_err_add Add record error -901 336723988 gsec_err_modify Modify record error -901 336723989 gsec_err_find_mod Find/modify record error -901 336723990 gsec_err_rec_not_found Record -901 336723991 gsec_err_delete Delete record error -901 336723992 gsec_err_find_del Find/delete record error -901 336723996 gsec_err_find_disp Find/display record error -901 336723997 gsec_inv_param Invalid

gbak_unk_device Device type not specified -901 336723983 gsec_cant_open_db Unable to open database -901 335740943 gfix_subs_name Subsystem name -901 336723984 gsec_switches_error Error in switch specifications seconds required -901 336723985 gsec_no_op_spec No operation specified -901 335740946 gfix_nval_req Numeric value between 0 and 32767 inclusive required -901 336723986 gsec_no_usr_name No user name specified specified -901 335544339 infinap Information type inappropriate for object specified -901 336723987 gsec_err_add Add record error Firebird 2.0 Error Codes SQLCODE GDSCODE SYMBOL TEXT -901 335740947 gfix_type_shut

gfix_subs_name Subsystem name -901 336723983 gsec_cant_open_db Unable to open database -901 336330767 gbak_unk_device Device type not specified -901 336723984 gsec_switches_error Error in switch specifications transactions -901 336723985 gsec_no_op_spec No operation specified -901 335740946 gfix_nval_req Numeric value between 0 and 32767 inclusive required -901 336723986 gsec_no_usr_name No user name specified for object specified -901 336723987 gsec_err_add Add record error -901 335544340 infona No information of this type available for object specified -901 336723988 gsec_err_modify Modify record error -901

............................................................................. 15 User management: gsec ................................................................................................. server fbserver (SS) or fb_inet_ server (CS) /bin Command-line tools isql, gbak, nbackup, gsec, gfix, gstat, etc. /bin Sample database employee.fdb /examples/ empbuild fb_in- et_server.exe (CS) \bin Command-line tools isql.exe, gbak.exe, nback- up.exe, gsec.exe, gfix.exe, gstat.exe, etc. \bin Sample database employee.fdb \examples\

thread-safe way to connect to a local server. For using single instances of the command-line tools (gsec, gbak etc.) it works just fine. By contrast, direct database connections - even multiple - under a change this password immediately using the gsec command-line utility. How to change the SYSDBA password Firebird comes with a command-line tool called gsec that is used to manipulate user accounts. Important With some Firebird installations, you can only run gsec if you are logged into the operating system as Superuser (root on Linux) or as the user the Firebird server process runs under. On Windows

the Same Task Using gsec An alternative is to use gsec with the -admin parameter to store the RDB$ADMIN attribute on the user’s record: gsec -add new_user -pw password -admin yes gsec -mo existing_user existing_user -admin yes gsec -mo existing_user -admin no  Depending on the adminstrative status of the current user, more parameters may be needed when invoking gsec, e.g., -user and -pass, or -trusted. Using database in which he has not been the granted the RDB$ADMIN role. Using gsec with RDB$ADMIN Rights To perform user management with gsec, the user must provide the extra switch -role rdb$admin. Granting the

Doing the Same Task Using gsec  With Firebird 3.0, gsec was deprecated. It is recommended to use the SQL user management statements instead. An alternative is to use gsec with the -admin parameter parameter to store the RDB$ADMIN attribute on the user’s record: gsec -add new_user -pw password -admin yes gsec -mo existing_user -admin yes gsec -mo existing_user -admin no  Depending on the administrative administrative status of the current user, more parameters may be needed when invoking gsec, e.g. -user and -pass, or -trusted. Using the RDB$ADMIN Role in the Security Database To manage user accounts through

is done entirely through SQL commands. Users of previous versions are probably familiar with the gsec utility for this task. It is still present, but deprecated, and it won’t be discussed here. 5.1 Legacy_UserManager (or Legacy_UserManager, Srp if you want to manage legacy accounts by default and/or through gsec). In user management statements, you can use the USING PLUGIN name clause to specify the user manager Firebird Guardian, 9 Firebird licenses, 4 Firebird project, 44 Firebird SQL, 35 Forced writes, 40 G gsec, 18 Guardian, 9 H Help, 42, 43 I IDPL, 4 Installation, 5 client-only, 13 drives, 7 script

the implementation. • User accounts can now be configured only by using the Services API or the gsec utility. • For backing up the security database, the Services API is now the only route. You can