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 !!!!!!

This is a known problem - expect improvements in the future.

> peraps any can help me to a method for protect my stored proc and table
> design !!!

1) put a lock on the server-room door
2) make sure the db file itself cannot be accessed except by
the Firebird server process
3) create a role SYSDBA by doing an INSERT into RDB$ROLES

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com