Subject | Re: [firebird-support] Users can create anything?!? |
---|---|
Author | Sam Hunt |
Post date | 2005-05-24T22:28:37Z |
richardghayward wrote:
Why are yours?
Your app should be providing appropriate privleges/access rights to
necessary data.
If your users need to query the data, provide them with a tool with a
dedicated read-only datasource.
To protect data and structures, only persons with genuine DBA
responsibilities should be allowed to log into an FB server. This is
why there are very few people who have DBA rights in an enterprise org
and getting them to chg structures is like pulling hen's teeth.
Hint: chg that "MASTERKEY" password and don't publish the new one.
>FB 1.5.2"Users" are NOT normally allowed to log into the FB server.
>
>I've just discovered that any user who can log into the server can
>create any table they want, and presumably other objects.
>
>I want to allow users to query tables but certainly not create new
>objects, unless they have been given permission to do so. MSSQL works
>like that. Surely it would make FB simply unsuitabe as a serious multi-
>user database.
>
>Please somebody tell me I'm mistaken!
>
>regards
>Richard
>
>
>
>
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://firebird.sourceforge.net and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
Why are yours?
Your app should be providing appropriate privleges/access rights to
necessary data.
If your users need to query the data, provide them with a tool with a
dedicated read-only datasource.
To protect data and structures, only persons with genuine DBA
responsibilities should be allowed to log into an FB server. This is
why there are very few people who have DBA rights in an enterprise org
and getting them to chg structures is like pulling hen's teeth.
Hint: chg that "MASTERKEY" password and don't publish the new one.