Maybe it's better to leave the SYSDBA ability and to make the database owner
possible to create/restore database with the additional [NO_SYSDBA] key, for
example, (default is SYSDBA). The existing part of the database security can be
carried from the isc4.gdb into the database file if NO_SYSDBA is specified.
This solution can satisfy all sides and old databases as well.

Dmitry Yemanov wrote:

> I agree it's not a bug. But it doesn't seem to be a right decision. I'd
> prefer to have all security implemented at the database level and have a
> full set of grants for system operations to drop the SYSDBA user and create
> any other accounts with the administration permissions I need. That's just
> my opinion, maybe I'm wrong. It was discussed in the various lists, but I
> don't know exactly which security way Firebird will go.

--
With respect
Alexander Rabtchevich