I have tried the following,

Update rdb$procedures set rdb$procedure_source = ''

It deleted the source text of the procedure leaving the BLR. The procedure
still works fine.

Before doing that, it would be wise to have that stuff validated by one of
the list gurus.

Salim

-----Original Message-----
From: Alexandre Benson Smith [mailto:iblist@...]

Alfredo wrote:

> I am developing a commercial application with Firebird, most of the
>
>
>>programming is inside the database (triggers, Stored procedures, views).
>>
>>
>So
>
>
>>I don't want my database to be open and view by anyone. So I changed all
>>users even the password for the SYSDBA account. As far as I know Firebird
>>manages all users access inside a database called security.fdb. I found
>>that if I Replace that database with a new one (with the original user:
>>sysdba and pwd: masterkey) can give access to the database and view all my
>>database programming. So the question is, is there a way to secure a bit
>>more the database. Because this is a major gap.
>>
>>Thanks in Advance
>>
>>

Alfredo,

1.) There is no security if you have no physical security
2.) If the root/administrator wish he could replace the file or
re-install the server
3.) Your customer should have sysdba anyway

If you want to hide the data from other aplications or block the access
from your client in anyway, I think the only solution is to encrypt the
data, and you know, for every closed door will be a locksmith around ;-)

see you !

--

Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br