Thanks for the code!
And thanks to tomkrej too for the other example!

<rant>

I was just wondering that in the 21st century, when there are code obfuscators and sophisticated security/encoding mechanisms everywhere, why on Earth is it such a big deal to make a DB unaccessible to intruders?

I mean I can't believe that no one who does serious software development has ever encountered this issue before... Is this the same for other enterprise level databases or is it just a "Firebird feature"?

Protecting their own code should be a high-level priority for every software developer!

</rant>

----- Original Message -----
From: Carlos H. Cantu
To: Zd
Sent: Wednesday, October 15, 2008 10:02 PM
Subject: Re: [firebird-support] How to hide the database structure from prying eyes?


Z> How exactly do I hide the triggers and stored procedures? Guess
Z> that would be better than nothing!

To hide source of procedures:

UPDATE rdb$procedures
SET rdb$procedure_source = NULL
WHERE ((rdb$system_flag = 0) OR (rdb$system_flag IS NULL))

To hide source of triggers:

UPDATE rdb$triggers a
SET rdb$trigger_source = NULL
WHERE ((rdb$system_flag = 0)
OR (rdb$system_flag IS NULL))
AND NOT EXISTS(
SELECT rdb$trigger_name FROM rdb$check_constraints
WHERE rdb$trigger_name=a.rdb$trigger_name)

For obvious reason, take care to not apply it in your "master"
database (the one you use for development).

Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br





[Non-text portions of this message have been removed]