Subject | FireBird security, where ? |
---|---|
Author | Charles-Henri Balet |
Post date | 2004-12-14T12:34:22Z |
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
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