Kevin Lingofelter wrote:

>In our case, we distribute an end user application with proprietary
>lookup data. Currently, all an end-user has to do is replace the
>security.fdb to gain SYSDBA privelages.
>
>Having the database either bound to a specific security.fdb file or
>having the users stored in the database itself would eliminate (well,
>greatly reduce the likelihood of) this problem.
>
>
>

I'm sorry, but if the file is readable, anyone can build a version of
Firebird with security turned off. Regretable, perhaps, but also
unavoidable.

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376