[Firebird-devel] gsec-issues with FB3.0

[Thomas B. <Tho...@as...>]

Hi everybody,

I'm having quite some problems with the permissions in FB3.0 and would
appreciate some hints on this.

I'm using gsec version WI-T3.0.0.30472 Firebird 3.0 Alpha 1.

First question:

gsec -user sysdba -password masterkey
GSEC> display
     user name                    uid   gid admin     full name
------------------------------------------------------------------------------------------------
SYSDBA                              0     0
BECKMANN                            0     0

Shouldn't SYSDBA show up with admin rights?
User BECKMANN were granted admin rights too
GSEC> modify BECKMANN -admin yes
but they won't show up either.

Now, I'd like to create a database (my server is running on 3051):

isql -user sysdba -password masterkey
CREATE DATABASE '127.0.0.1/3051:c:\temp\test.fdb' USER 'SYSDBA' PASSWORD
'masterkey';

But I get:
Statement failed, SQLSTATE = 28000
Your user name and password are not defined. Ask your database
administrator to set up a Firebird login.

Issuing
CREATE DATABASE 'c:\temp\test.fdb';
works fine.

Now, I try to connect to that database:
isql 127.0.0.1/3051:c:\temp\test.fdb -user sysdba -password masterkey
Does not work:
Statement failed, SQLSTATE = 28000
Your user name and password are not defined. Ask your database
administrator to set up a Firebird login.
Use CONNECT or CREATE DATABASE to specify a database

Using
isql 127.0.0.1/3051:c:\temp\test.fdb -user beckmann -password SomePwd
works fine - I understand, that my Windows-credentials have been used to
create the database.

Now:
gsec -database c:\temp\test.fdb
GSEC> display
Dynamic SQL Error
SQL error code = -204
Table unknown
PLG$SRP_VIEW
At line 1, column 129

After adding SYSDBA
GSEC>add SYSDBA -pw masterkey -admin yes
GSEC> display
GSEC>
SYSDBA will not show up, but the error is gone...

Issuing
gsec -database 127.0.0.1/3051:c:\temp\test.fdb -user beckmann -password
SomePwd
GSEC> display
crashes gsec (Windows exception), gsec shuts down, server is still up, while
gsec -database 127.0.0.1/3051:c:\temp\test.fdb -user sysdba -password
masterkey
works fine.

gsec -database c:\temp\test.fdb -user sysdba -password masterkey
GSEC> display
     user name                    uid   gid admin     full name
------------------------------------------------------------------------------------------------
SYSDBA                              0     0
GSEC>

Now, I do
gbak -b c:\temp\test.fdb c:\temp\test.fbk -user sysdba -password masterkey
gbak -r c:\temp\test.fbk c:\temp\test1.fdb -user sysdba -password masterkey

Than
gsec -database 127.0.0.1/3051:c:\temp\test1.fdb -user sysdba -password
masterkey
GSEC> display
crashes gsec, while
gsec -database c:\temp\test1.fdb -user sysdba -password masterkey
works fine.

Finally
gbak -b c:\temp\test.fdb c:\temp\test.fbk
gbak: ERROR:Unable to perform operation.  You must be either SYSDBA or
owner of the database
gbak:Exiting before completion due to errors
I still am the owner of the database (I hope ;-))
gbak -b c:\temp\test.fdb c:\temp\test.fbk -user beckmann -password SomePwd
returns the same error (this behavior is already in the tracker and
confirmed as beeing erroneous).

Hm... I'm getting quite confused...
Some of this behavior might be a bug, but some might be intended...

Thank you for some hints on this! Thomas
-- 
Mit freundlichen Grüßen,

Thomas Beckmann
Diplom-Informatiker

Wielandstraße 14c • 23558 Lübeck
Tel +49 (22 25) 91 34 - 545 • Fax +49 (22 25) 91 34 - 604
Mail tho...@as... <mailto:tho...@as...>

ASSFINET-Logo

*ASSFINET Dienstleistungs-GmbH*
Max-Planck-Straße 14 • 53501 Grafschaft bei Bonn
in...@as... <mailto:in...@as...> • www.assfinet.de
<http://www.assfinet.de/>

Geschäftsführer: Dipl. Wirtschaftsinformatiker Marc Rindermann
Registergericht Koblenz HRB 23331

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der
richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist
nicht gestattet.