Skip to content
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

Installation of Firebird 3.0 beta 2 totally ignores my sysdba login information [CORE5126] #5410

Open
firebird-automations opened this issue Mar 3, 2016 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Danniel Corbit (dcorbit)

Installation of Firebird offers a screen to set the system DBA username and password at install time.
It allowed me to fill out the form, but totally ignored the results.

You cannot change the system owner (for instance) from SYSDBA to SA
You cannot change the system owner password. No matter what you type (and it does get accepted!) the sysdba password is masterkey when you are done.
This is a security breach so severe that the database is unusable.

Commits: 88923cb

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Do you really speak about BETA 2? Or about RC2?

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Danniel, I do not know what exactly asks windows installer at that screen, but changing system owner from SYSDBA to something else is definitely impossible at this stage. It's hardcoded string.

To help us better solve your problem please answer 2 questions:
1. What client version did you use to connect to firebird 3.0 server? Native (3.0) or some previous version?
2. Does password 'masterke' (8 letters, no final 'y') let you connect to server?

@firebird-automations
Copy link
Collaborator Author

Commented by: Danniel Corbit (dcorbit)

I used flamerobin 0.9.2.1851

If there is a different procedure that must be used, what is the procedure?

@firebird-automations
Copy link
Collaborator Author

Commented by: @reevespaul

Beta 2 was released eight months ago and has been superceded by two release candidates.

My first recommendation would be to be sure to test with the most recent version. Also, be sure to test with a clean install, by ensuring that no traces of a previous firebird 3 install remain. You can use unins000.exe /clean for that (or just delete the old config files manually.)

The option to change the name of SYSDBA at install time will be removed before the next release. So don't waste time testing that.

And, finally, I doubt that flamerobin 0.9.2.1851 is ready for Firebird 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant