New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GSEC does not authenticate user correctly [CORE1778] #2203
Comments
Modified by: Svend Meyland Nicolaisen (smndk)description: When starting gsec without parameters it does not prompt that user name and password are required. ==== Example When GSEC has been started without parameters on Windows XP, the add, delete and modify commands works as it would if valid authentication had been performed. When GSEC has been started without parameters on Windows 2000, the add command causes an abnormal program termination. ISQL has similar problems. => When starting gsec without parameters it does not prompt that user name and password are required. ==== Example When GSEC has been started without parameters on Windows XP, the add, delete and modify commands works as it would if valid authentication had been performed. When GSEC has been started without parameters on Windows 2000, the add command causes an abnormal program termination. ISQL has similar problems. |
Modified by: @dyemanovassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff What about utilities behavior when started without login/password parameters - please see release notes: trusted authentiaction. I suppose on XP you login as member of admins group, but on 2k - not as a member of that group. Abnormal program termination when error should be displayed in gsec appears fixed in RC2 - please retry with it, it will be available in a few days. |
Modified by: Svend Meyland Nicolaisen (smndk)Version: 2.1 RC2 [ 10250 ] |
Commented by: Svend Meyland Nicolaisen (smndk) Just testet with Firebird 2.1 RC2. GSEC still behaves incorrectly when using trusted authentication on Windows 2000. |
Commented by: @AlexPeshkoff Can you be more specific, please? |
Commented by: Svend Meyland Nicolaisen (smndk) Using trusted authentication: A) I expect Display to display the users in the security database. B) Add results in an abnormal program termination. ===> Example start C:\Program Files\Firebird\Firebird_2_1>bin\gsec C:\Program Files\Firebird\Firebird_2_1> <=== Example end Using trusted authentication: C) I expect Modify to change the password for sysdba. ===> Example start C:\Program Files\Firebird\Firebird_2_1>bin\gsec <=== Example end Authentication using SYSDBA: D) Shouldn't it be possible to change the password for SYSDBA and then be able to continiue to use GSEC without restarting it? ===> Example start C:\Program Files\Firebird\Firebird_2_1>bin\gsec -user SYSDBA -password masterkey <=== Example end Hope this help. |
Commented by: Svend Meyland Nicolaisen (smndk) DR. Watson dump for abnormal program termination: Application exception occurred: *----> System Information <----* *----> Task List <----* (00400000 - 0041A000) State Dump for Thread Id 0xab0 eax=00d1000c ebx=00000012 ecx=0012ef88 edx=00d1000d esi=00d1000c edi=0012ed04 function: <nosymbols> *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name *----> Raw Stack Dump <----* |
Commented by: @AlexPeshkoff A. No matter of auth used, display shows all users only to SYSDBA. When legacy auth is used, it shows to non-SYSDBA only current user. This is normal security measure, is not it? B. Sorry, I can't reproduce AV in gsec. I get correct and well looking error: C. gsec has no problems changing SYSDBA password in trusted auth provided you are a member of admin group. D. Please add it (possibility to change the password for SYSDBA and then be able to continiue to use GSEC without restarting it) as a separate feature request to the tracker. |
Commented by: Svend Meyland Nicolaisen (smndk) A. The user I am using is a member of the local Administrators group on the computer. It surdenly has administrative rights on the PC. B. I will try to produce a stack back trace later. C. As A. D. OK. |
Modified by: Svend Meyland Nicolaisen (smndk)environment: Windows 2000, Windows XP. => Windows 200 |
Modified by: Svend Meyland Nicolaisen (smndk)environment: Windows 200 => Windows 2000 |
Commented by: @AlexPeshkoff gsec operation can be now successfully continued after SYSDBA's password change. The rest of reported issues (AVs in gsec) are not reproduced. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Alpha 1 [ 10224 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Svend Meyland Nicolaisen (smndk)
When starting gsec without parameters it does not prompt that user name and password are required.
==== Example
C:\Program Files\Firebird\Firebird_2_1\bin>gsec
GSEC>
==== Example end
When GSEC has been started without parameters on Windows XP, the add, delete and modify commands works as it would if valid authentication had been performed.
When GSEC has been started without parameters on Windows 2000, the add command causes an abnormal program termination.
ISQL has similar problems.
The text was updated successfully, but these errors were encountered: