Firebird 3 Blocking Sysdba
16:13, Thomas Beckmann wrote: Finally gbak -b c:temptest.fdb c:temptest.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:temptest.fdb c:temptest.fbk -user beckmann -password SomePwd returns the same error (this behavior is already in the tracker and confirmed as beeing erroneous).This one has already been fixed.Dmitry. On Thursday 04 July 2013 15:56:07 Thomas Beckmann wrote: gsec -database 127.0.0.1/3051:test.fdb -user beckmann -password SomePwd GSEC display Dynamic SQL Error SQL error code = -204 Table unknown PLG$SRPVIEW At line 1, column 129 Very interesting.Yes, very interesting.I saw that error recently. I was trying to access gsec before I had addedSYSDBA.
Once SYSDBA was added and I managed to login correctly as SYSDBA (noteasy) the message went away.Presumably you have set AuthServer correctly? And restarted the serverperhaps?Paul-Paul ReevesSupporting users of Firebird. On 07/04/13 18:16, Paul Reeves wrote: On Thursday 04 July 2013 15:56:07 Thomas Beckmann wrote: gsec -database 127.0.0.1/3051:test.fdb -user beckmann -password SomePwd GSEC display Dynamic SQL Error SQL error code = -204 Table unknown PLG$SRPVIEW At line 1, column 129 Very interesting.
Yes, very interesting. I saw that error recently. I was trying to access gsec before I had added SYSDBA. Once SYSDBA was added and I managed to login correctly as SYSDBA (not easy) the message went away.
Presumably you have set AuthServer correctly? And restarted the server perhaps? PaulI've fixed diagnostics here. Now under this conditions one gets:- Install incomplete, please read chapter 'Initializing securitydatabase' in Quick Start GuideIt was always a case when trying to login to the server, missing correctdata structures in security3.fdb. Now same code is added to managementplugin.What's bad is that we still do not have Quick Start Guide for FB3 (ormay be I'm missing something?) and therefore no such chapter.As a solution I can suggest to writedoc/README.Initializingsecuritydatabase and add appropriate text toerror message.Next question.What more reasons do we have (with mentioned changes done and fixedservices code for -display switch) to use old security database formatin default windows install?I want to ask to rollback installer changes and use SRP as defaultplugin in FB3 as it was initially designed.A.
On Monday 15 July 2013 15:13:54 Alex Peshkoff wrote: Next question. What more reasons do we have (with mentioned changes done and fixed services code for -display switch) to use old security database format in default windows install? I want to ask to rollback installer changes and use SRP as default plugin in FB3 as it was initially designed.One problem I found is that I couldn't log in to an FB3 server on windows froma linux fb2.5 client. How is that done without the legacy authentication?The main reason I see for using the old security database format in theinstaller is to make it easy for our users to get started with FB3.
Thedocumentation is still incomplete and things don't always quite work. Bykeeping the old sysdba/masterkey login users should at least be able to getstarted.It is up for discussion as to whether it is the default click through optionor not.
Users are not against change, they just like to do it at their ownpace. Hopefully the feedback we get during alpha/beta will help us make theright decision.Paul-Paul ReevesSupporting users of Firebird. On 07/15/13 18:19, Paul Reeves wrote: On Monday 15 July 2013 15:13:54 Alex Peshkoff wrote: Next question. What more reasons do we have (with mentioned changes done and fixed services code for -display switch) to use old security database format in default windows install? I want to ask to rollback installer changes and use SRP as default plugin in FB3 as it was initially designed. One problem I found is that I couldn't log in to an FB3 server on windows from a linux fb2.5 client. How is that done without the legacy authentication?No way.
I would like recommend that you always check the price To get a cheap price or large amount.
From any client The main reason I see for using the old security database format in the installer is to make it easy for our users to get started with FB3. The documentation is still incomplete and things don't always quite work. By keeping the old sysdba/masterkey login users should at least be able to get started.Certainly in A1 security is not real goal:-)But let's have an exact plan - when do we start to use SRP by default? It is up for discussion as to whether it is the default click through option or not.On my mind ability to lower security level can't be available by default.Please also take into an account that using legacy plugin toauthenticate breaks wire encryption. Users are not against change, they just like to do it at their own pace. Hopefully the feedback we get during alpha/beta will help us make the right decision.Most of people will think about security after compromising firebirdinstallation.
On Tuesday 16 July 2013 15:17:49 Alex Peshkoff wrote: On 07/15/13 18:19, Paul Reeves wrote: One problem I found is that I couldn't log in to an FB3 server on windows from a linux fb2.5 client. How is that done without the legacy authentication? No way. From any client And this is by design. We have to make that step or we will always have to stay with that 8-byte passwords.So we need to get the message across that using the old security means stayingwith 8-byte passwords, ie almost no security. Certainly in A1 security is not real goal:-) But let's have an exact plan - when do we start to use SRP by default?My feeling is that we should support click-through install on windows withSYSDBA/masterkey for alpha and beta.
And that from RC1 we disable that as adefault (but users can choose the option if they wish.)This plan should be clearly documented and we should listen to feedback. On my mind ability to lower security level can't be available by default. Please also take into an account that using legacy plugin to authenticate breaks wire encryption.That is another point that needs to be made clear - new security allows wireencryption.I know everything is more or less documented. I just have the feeling that thepresentation needs to be improved so that (old) users can see at a glancewhat has changed and why they should change their old ways.Paul-Paul ReevesSupporting users of Firebird. -Oprindelig meddelelse- Fra: Paul Reeves mailto:preeves@. Sendt: 17.
Firebird 3 Blocking Sysdba User
Juli 2013 12:00 Til: For discussion among Firebird Developers Emne: Re: Firebird-devel gsec-issues with FB3.0 On Tuesday 16 July 2013 15:17:49 Alex Peshkoff wrote: On 07/15/13 18:19, Paul Reeves wrote: One problem I found is that I couldn't log in to an FB3 server on windows from a linux fb2.5 client. How is that done without the legacy authentication?
No way. From any client And this is by design. We have to make that step or we will always have to stay with that 8-byte passwords. So we need to get the message across that using the old security means staying with 8-byte passwords, ie almost no security. Certainly in A1 security is not real goal:-) But let's have an exact plan - when do we start to use SRP by default?
My feeling is that we should support click-through install on windows with SYSDBA/masterkey for alpha and beta. And that from RC1 we disable that as a default (but users can choose the option if they wish.)This will be a smart move as testing by 'swapping' versions will be a lot easier. But I also strongly support that backwards compatibility with things that we actually want to abandon should not be the strongest priority!
FB3 is new stuff - with the good things from the past remaining, and the bad ones at least properly hidden away! Just like wire encryption to my understanding is a must as default security feature in the final version.Best regardsPoul.
I'm using firebird with docker with the image jacobalberty/firebird:2.5.8-scI use it in local and in the remote server.