>>In other words, you want to rename SYSDBA user. Why do you
>>think it would lower basic database hackability ?

> Well SYSDBA is the first login a guy will try with masterkey
> as the password, I just want to foul the first login.

Changing the administrator user name is a recognised form of
protection against brute force network based attacks. Its
not a substitute for a good password and other forms of
protection, its merely another level of protection, a form of
security by obscurity. The benefit is probably dubious, since
discovery of the administrator user name may not be difficult,
depending on the many factors.

The logic is; If a stranger to your system does not know any
of the administrative user names then a brute force attack is
stuck with guessing both the user name and the password, adding
a level of difficulty.


However for those that have misread this idea: changing the
SYSDBA user name, or deleting SYSDBA, offers NO BENEFIT AT ALL
in terms of protection against database files copied to other
servers (even assuming you were able to revoke SYSDBA access
within that file). Several idea off the top of my head...

- I compile a version of FB that ignores privileges - I dont
imagine that would be difficult but have never tried it.

- I use a hex browser to scan for owner of the database and
its objects (or the user privileges). Then I setup my own
system with the same user name and I am in.

The short story: Give a user direct access to the file and
all bets are off. If you want the database data secure then
secure the database file(s).


As for network access security - well changing the SYSDBA
user name may help, but the better option is to improve the
authentication system. AFAIK this is being (or has been)
discussed in the architect or devel lists (the correct place
for such discussions).

--
Geoff Worboys
Telesis Computing