hi,

how to actually delete those source from the database?

well, i suppose we can always keep our source and update for the
customer when necessery right?


On Sun, 27 Mar 2005 14:36:53 +0200, Alexander Gräf
<graef@...> wrote:

>
>
> Hello Sue,
>
> if you're distribution your fdb to the customer, there is no way to deny access for the SYSDBA. However, you can delete the source code from the SPs, Triggers etc., because only the compiled form is needed for execution. Anyway, you will make the job of the DBA harder, because he cannot lock into the source (maybe some day he needs to change something), and the compiled form isn't hard to reverse engineer, so this is no real protection for your code. I doubt there is any protection at all, except operating your own server and never let the customer get your fdb.
>
> Regards, Alex
>
> > -----Ursprüngliche Nachricht-----
> > Von: suechubster [mailto:suechubster@...]
> > Gesendet: Sonntag, 27. März 2005 13:42
> > An: firebird-support@yahoogroups.com
> > Betreff: [firebird-support] Preventing sysdba accessing fdb
> > stored porocs
> >
> >
> >
> >
> > When distributing a fdb to customers is there anyway to
> > prevent the sysdba from accessing the tables, stored procs,
> > etc on that fdb?
> > (I am assuming that sysbda may needs to admin other fdb on the server)
> >
> > Sue
> >
> >
>
> Yahoo! Groups Links
>
>
>
>
>