At 10:43 AM 3/22/01 +0200, Vince Duggan wrote:

>Dmitry,
>
>I can see their problem, but one should not allow anyone direct access to the
>database. If you do not have direct access, then you cannot execute the

commands

>to create tables, databases etc. All database access is 'hidden' in the

web app,

>i.e by using PHP, Perl or something similar.
>
>It is simple enough to prevent anyone from connecting directly to the

database

>from outside: block port 3050 for example.
>
>If someone can hack in and execute commands directly on the database, then

there

>is another security problem. InterBase is not the problem in this case.
>

Whether or not allowing physical access to 3050 is a good idea,
everything that a server is capable of doing should be under
security control, specifically including database and table
creation. Security is not robust until it is "provably"
correct (I don't actually believe for a wit that provability
means anything, but provably insecure is something else).

Or, to apply another test, when a potential customer tells you
he can't use your product, believe him.

Jim Starkey