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 incorrectly processes some switches [CORE1263] #1686
Comments
Modified by: @dyemanovassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff Any of switches -user, -password, -database and -trusted are not accepted any more in interactive mode. |
Modified by: @AlexPeshkoffFix Version: 2.1 Beta 1 [ 10141 ] |
Commented by: @pcisar Fix verified for Beta 1, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 12121 ] => Firebird [ 15208 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Kuznetsov Eugene (eugene)
Is related to QA157
In FB 1.5.4 CS adding user in GSEC's interactive mode by commands
add testuser -pa 111
add testuser -pas 111
...
add testuser -password 111
don't leave to error, but in that case new user gets NULL password.
In FB 2.0.1 the constraint for RDB$PASSWD was added and these commands return
validation error for column RDB$PASSWD, value "*** null ***"
Suggestion: switches -pa, -pas, ..., -password should be considered as incorrect and "invalid switch specified" should be returned in that case.
With best regards, Eugene
Commits: 4487203
The text was updated successfully, but these errors were encountered: