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

Fb3 Beta1 RlsNotes - 8 Dec 2014 - v.0300-17, page 91: the setup-description assumes security3.fdb contains sysdba account [DOC100] #109

Closed
firebird-automations opened this issue Dec 23, 2014 · 8 comments

Comments

@firebird-automations
Copy link

Submitted by: Peter Vandel (petervandel)

*** Solved in new Document version v.0300-18 ***
As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

@firebird-automations
Copy link
Author

Commented by: Peter Vandel (petervandel)

Applies to "Firebird-3.0.0.31374-0_Win32_Beta1.zip", where security3.fdb is empty.
Windows Installer may fill security3.fdb with a sysdba account.

@firebird-automations
Copy link
Author

Modified by: @paulvink

assignee: Paul Vinkenoog [ paulvink ] => Helen Borrie [ helebor ]

@firebird-automations
Copy link
Author

Commented by: Peter Vandel (petervandel)

As a last comment, gsec is mentioned three times as deprecated in this same Release Notes document. May be better to add an ISQL-example instead.

@firebird-automations
Copy link
Author

Commented by: @helebor

1. Please describe how the instructions on P. 91 are not working for you. You need to be looking at the version from 8 December 2014 - Document v.0300-18

2. If you want something improved in the engine, filing a DOC ticket is not the way to register it, as nobody but the documenters will see it..

3. "Deprecated" means the feature will not be developed further and, in some future release (not this one) is likely to be removed. Essentially, gsec continues to work as before with the default security database. It does not work with alternative security databases.

@firebird-automations
Copy link
Author

Commented by: Peter Vandel (petervandel)

What a coincidence: Two Fb3.0B1 Release Notes with the same date (8 December 2014): Document v.0300-17 and Document v.0300-18.
Page 91 of v.0300-17 incorrectly contains a modifiy command.
Page 91 of v.0300-18 correctly contains an add command.
Issue solved.

@firebird-automations
Copy link
Author

Modified by: Peter Vandel (petervandel)

description: As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password.
Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

=>

As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

summary: Fb3 Beta1 RlsNotes, page 91: discrepancy between usage description of gsec (to set up security3.fdb) and current reality => Fb3 Beta1 RlsNotes - 8 Dec 2014 - v.0300-17, page 91: the setup-description assumes security3.fdb contains sysdba account

@firebird-automations
Copy link
Author

Modified by: Peter Vandel (petervandel)

priority: Major [ 3 ] => Minor [ 4 ]

description: As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected. => *** Solved in new Document version v.30300-18 ***
As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

@firebird-automations
Copy link
Author

Modified by: Peter Vandel (petervandel)

description: *** Solved in new Document version v.30300-18 ***
As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

=>

*** Solved in new Document version v.0300-18 ***
As long as security3.fdb contains no users, the user sysdba need to be added to it, prior to enable gsec (and isql) to modify the sysdba password. Either security3.fdb should be shipped containing user sysdba or the text in the release notes needs to be corrected.

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

3 participants