Anyone who can reach your database file physically, can get hold of your
data. It is possible to delete the readable version of stored procedures
and triggers(?), but the only proper way to protect your system is to
protect your files so that no-one can touch them except through the
database engine (of course, SYSDBA needs to be trusted and have a password
deviating from the "interbase standard" masterkey).

Someone mentioned that creating a role named SYSDBA could prevent SYSDBA
from having access, but I would never do such a thing myself since I do not
know enough about the side effects this could have, it just sounds scary.

Set

At 09:21 23.05.2003 +0000, you wrote:

>Hi list,
>what happens to my DB, with my password / user name, in a machine
>with masterkey/SYSDBA? Can it be opened?
>In the affermative is it possible to avoid opening?
>
>Any help appreciated.