> >NOW - this makes absolutely no difference when you think of just
> connecting
> >to a database with a username and password. But when you wish to
> allow users
> >the ablity to edit their own password and (most importantly) a
> SYSDBA to log
> >on to your application, see a list of all users, edit/reset
> their passwords,
> >delete users and also conveniently edit his/her own password... then you
> >need the path to the security database.
>
> Why? How would it be used where the (safer) alias would not? (Apart from
> providing compatibility with InterBase, that is...but then, compatibility
> with InterBase isn't quite what most people would view as a security
> enhancement...)
>
> ./heLen

there are no aliases in my setup. I have 2-3 hundred new installs where
people will be invited to download and install the superserver from
firebirdsql.org.
I won't have anything to do with their installation I hope.
The only thing they will ever do is copy the single user database to a place
on the server machine and now unfortunately stop the server, copy a new
security.fdb file over and restart the server. Not having them have to
install an alias to the security database is just one less step to get them
in a mess.
Alan
PS - but I still need the path to the security DB