IB6.5 has enhanced metadata security. Not sure about how 'secure'
this is, since in the specs they mention only that the new
feature 'protects the data from modification by unauthorized users'.
I presume this means it is hidden.

FB has very limited metadata security. The only way to keep anyone
from examining DDL, and only for triggers and procedures, is:

UPDATE RDB$TRIGGERS SET RDB$TRIGGER_SOURCE = NULL

UPDATE RDB$PROCEDURES SET RDB$PROCEDURE_SOURCE = NULL

Ensure you have backup copies of your DDL prior to erasing the source
in the db. Also, there may be system triggers and procedure source
that you should not delete! So be selective going about it.

Regards,
Andrew Ferguson
-- Lemurs check in, but they don't check out.

--- In ib-support@y..., "alnufari" <omar2000@s...> wrote:
> I have that database with many tables, triggers, SP, views.
MyClient
> is a Delphi application with IBX. Almost all of the work is done on
> the server. I'll ask the same old question again. What is the best
> way to protect my metadata? I Don't want any one, not even the
> administrator to look at it. I might define a fictive admin in my
> clients, change sysdba's password after install (using IBInstall
then
> IBSecurity) encrypte the password but I also need to protect the
> metadata against an uninstall and reinstall (using the official
> setup) of interbase. Is there any wawy to change some system data
> information in my db so it can't show it's metadata to any one but
> it's owner (creator)? My DB is not included in my package but
created
> from script at run time. Here I always encrypt the script so I have
> no problem. The question is once the db is there!!!
> I use IB 6, Should I expect something better from IB6.5 or FB?
> Thanks for any Help
> Omar