It is not always obvious to newcomers that there is a distinction between server access And database security. When you “log into” a Firebird database using isql or your favorite admin tool, you always supply a user name and password, along with server, port (sometimes), and path parameters. Whenever you do this, you are logging into theserver and opening an attachment to a database.
If the database does not exist yet and you have started isql from the command line with no parameters, then two things are “givens”:
Password access is always required to log into the server. Once in, you can attach to any database. What you can do, once attached, depends on SQL privileges, which are stored within the database. The SYSDBA user has full destructive rights to every database and every object within it. The owner (the user that created the database) has automatic rights to the database, although not to any objects within it that were created by other users. SQL privileges are opt-in. That means that, although any user with server access can attach to any database, the user will have no rights to do anything to anything, other than what has been explicitly or implicitly granted to it by the owner, using GRANT statements.
The issues of server access and database security are discussed in detail in Part Eight.
ISC_USER and ISC_PASSWORD
It is possible to set up the two environment variables ISC_USER and ISC_PASSWORD on the server, to avoid the need to write and store scripts that contain passwords “in clear.” You will be able do everything that the named user is allowed to do, without needing to supply credentials. This feature is handy for administrative tasks, but it must be used with a high level of caution because it leaves your database access open to any local user who happens upon your command shell.
If you want to play with fire, set these two variables permanently. If you want to have that extra level of convenience and script security, set them temporarily each time you want them and be certain to reset them whenever you leave your console.
On Linux, in the same shell from which you will launch the application, type]# setenv ISC_USER=SYSDBA ]# setenv ISC_PASSWORD=masterkey
To unset, either use this:]# setenv ISC_USER= ]# setenv ISC_PASSWORD=
or simply close the shell.
On Windows, go to the command prompt and type
To unset, typeset ISC_USER= set ISC_PASSWORD=
Firebird Related Interview Questions
|RDBMS Interview Questions||MySQL Interview Questions|
|Linux Interview Questions||Mac OS X Deployment Interview Questions|
|Windows Administration Interview Questions||Windows Server 2003 Interview Questions|
|SQL Interview Questions||NoSQL Interview Questions|
|Advanced C++ Interview Questions|
Introduction To Client/server Architecture
About Firebird Data Types
Date And Time Types
Blobs And Arrays
From Drawing Board To Database
Creating And Maintaining A Database
Firebird’s Sql Language
Expressions And Predicates
Querying Multiple Tables
Ordered And Aggregated Sets
Overview Of Firebird Transactions In
Programming With Transactions
Introduction To Firebird Programming
Developing Psql Modules
Error Handling And Events
Security In The Operating Environment
Configuration And Special Features
Interactive Sql Utility (isql)
Database Backup And Restore (gbak)
Housekeeping Tool (gfix)
Understanding The Lock Manager
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.