>
> LOL it's longer than I thought so I don't remember it exactly. I did
> the
> trick with adding SYSDBA role (using insert command into RDB$ROLES)
> and

that's correct. There IS an RDB$ROLES table in the security database-it's a
standard database after all. But this is never used.

> I'm pretty sure that I added this role into RDB$ROLES into security
> database. I still have a source code, that makes some changes in
> security database and one of this change is granting all rights to my
> DB
> owner user with grant option.

You don't declare a role to connect to the security db. It's only used to
connect to the DB in question. If you did indeed create a role in the
security DB I'm pretty sure it did nothing.
If you declare a role called SYSDBA in a database and you do not grant this
role to SYSDBA the person and you only grant the SYSDBA role to other
persons, then the SYSDBA on a foreign server cannot get access to the
database.
If, however, you view the database with a hex viewer you will soon see a
list of users of the database. They are in clear text. You can then create
one of these users in your security db with a password of your choosing, and
you then have access to this database.
We can only hope that the original OP who asked this question is doing this
in an honest endeavour.
Alan

>
> Milan
>
> >
> > I've used that trick in the past, but I removed it long
> > > time ago and didn't read any change of this. So it's my mistake and
> I'm
> > > sorry for my bad information.
> > >
> > > Milan
> > >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org 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
>
>
>