Rick Debay wrote:

> You are correct, I just checked our rpm install of the beta and while
> the comment is still there, the code is not. I will have to check the
> tarball install, I could swear it contained the old script. Or perhaps
> we installed the wrong tarball on the test system.
>

post-install script in rpm and tar is exactly the same - it's simply the
same file. But as far as I remember you were initially talking about
1.5? In it there IS the sysdba password, and for security reasons file
must be 0600.

>
>>For production system suggested feature is a bad thing.
>
> I don't understand. Anyone who can run kill as root can of course stop
> the server. But the comment in the script suggested that only root
> should be able to stop the server.

I plan to review whole linux setup soon, including comments fixing.

> I wanted to make sure that any
> shutdown scripts, programs, etc belong to the firebird group, and not
> root.
>

Why? Usre 'firebird' is a pseudo-user, in which context fbserver runs.
Suppose someone (bad guy) found a way to run his code in context of
firebird server (due to some BOF, bad firebird.conf - or something
else). If some programs, scripts belong to user 'firebird', he can
modify it. With current root ownership - he can't. Why do you want to
make production system less protected?

> On our test system they're all owned by
> root (We log on as root to the test systems. In production that's not
> done, of course).

Normally all services on production system are controlled by root. Did
you try, for example, to restart named beeing a member of named group?

Group firebird was primarily designed for embedded access to the server.
Please agree, that access to the server and ability to start-stop it are
a bit different things. For today, two users can stop server - root and
firebird. And for me, this is absolutely correct.