Table definitions must be available simply
because client tools need them. Simply the
system will become unusable.
Stored procs and triggers source can be
deleted from system talble that store them.

On Tue, 14 Dec 2004 16:34:22 +0400, Charles-Henri Balet wrote:

>
>
>Hello,
>
>I'm want to protect my database for reverse engeenering (stored proc and
>table fields definition), after one day
>of test I think it's not possible, it's very simple for anything to force
>the security of interbase and firebird
>
>sample : you create a database .fdb and you crypt a password for SYSDBA
>access of server and ? it's very simple
> to acced of this fdb database, you copy the fdb file on
>other computer with local firebird server, your login
> on SYSDBA with your new password and you access on all
>table's and stored proc ??????? you say security !!!!!!
>
>peraps any can help me to a method for protect my stored proc and table
>design !!!
>
>many thanks
>
>balet charles-henri
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>