Subject | Re: [firebird-support] isql client and passwords |
---|---|
Author | Ian Barwick |
Post date | 2004-08-14T11:33:38Z |
On Saturday 14 August 2004 12:51, Alan McDonald wrote:
I have just installed Firebird on a Linux machine which has never
had Firebird on it before; using FirebirdSS-1.5.1.4481-0.i686.rpm.
As a normal Linux user I can then immediately execute
/opt/firebird/bin/isql /opt/firebird/examples/employee.fdb
or
/opt/firebird/bin/isql localhost:/opt/firebird/examples/employee.fdb
and connect to the database without providing _any_ username or
password (even as environment variables). I can execute DML and DDL
statements, and also create new databases.
Connections to the database using the machine's external interface or from
another machine only work with correct user name and password.
It appears then that local connections are not restricted; how can I prevent
this?
Thanks
Ian Barwick
> > Now for a silly question: I am working with a fresh RPM install of 1.5.1This is a different problem, sorry for the confusion.
> > superserver and have only changed the SYSDBA password.
> > However I can connect to the database, create databases etc.
> > without providing
> > any username / password (either as command line options or as environment
> > variables). How can I prevent this?
> >
> > Ian Barwick
>
> check your environment variables again. They must be set.
> Alan
I have just installed Firebird on a Linux machine which has never
had Firebird on it before; using FirebirdSS-1.5.1.4481-0.i686.rpm.
As a normal Linux user I can then immediately execute
/opt/firebird/bin/isql /opt/firebird/examples/employee.fdb
or
/opt/firebird/bin/isql localhost:/opt/firebird/examples/employee.fdb
and connect to the database without providing _any_ username or
password (even as environment variables). I can execute DML and DDL
statements, and also create new databases.
Connections to the database using the machine's external interface or from
another machine only work with correct user name and password.
It appears then that local connections are not restricted; how can I prevent
this?
Thanks
Ian Barwick