[firebird-support] Re: Enable authorization for legacy Firebird clients
Hi, My point is that I have not created SYSDBA with masterke password and I still can connected database with these. "Note that you have two entries for User1, one for the SRP plugin and the other for the Legacy Authentication." Now I understand logic that there are 2 different user for SYSDBA but shouldnt firebird installer have second input for legacy authentication user creation. My worry is that someone install firebird with legacy authentication and don't change this user password afterwards. - Tomi
Re: [firebird-support] Enable authorization for legacy Firebird clients
HI Em 7/7/2016 05:49, tomi.j...@oscar.fi [firebird-support] escreveu: Hi, I don’t know if i have understand “Enable authorization for legacy Firebird clients” right but.. I just installed Firebird 3 to new development server and checked “Enable authorization for legacy Firebird clients” so I can test connection from old 2.5 clients. In this installation window I create random password like “pass1234”. When I connected to database from same server connection is okay with “pass1234”. But when I tried to connect from old development server where firebird 2.5 is installed with “pass1234” I get error “Your user name and password…”. My surprise was when I tried connect database from old server with pasword “masterkey” that connection is succesfully. I have not created user SYSDBA with “masterke” password and still I get connected in database. So my question is that should this be like this? Best regards, -Tomi I don't know how are your configurations, but to enabled Legacy Auth you must change: AuthServer = Srp, Legacy_Auth UserManager = Srp, Legacy_UserManager WireCrypt = Enabled after that, the server is enabled to authenticate using the old protocol. I think you are in this point, but are unable to authenticate from other users because the other users was create by the default plugin (SRP), you must create those users using the Legacy_UserManager plug in.The SYSDBA was automatically created by the installer using the Legacy_UserManager plugin this is the reason you could connect using SYSDBA. connect to your database and execute the following: select sec$user_name, sec$plugin from sec$users; You should see something like: SEC$USER_NAME SEC$PLUGIN === === User1 Srp User2 Srp This indicates that the users are created but with the new SRP plugin, to authenticate legacy users you need to create them using the legacy user manager plugin. execute this: create user User1 password 'pas1234' using plugin Legacy_AuthManager; commit; after that execute this: select sec$user_name, sec$plugin from sec$users; You shoud see: SEC$USER_NAME SEC$PLUGIN === === User1 Srp User2 Srp User1 Legacy_UserManager Note that you have two entries for User1, one for the SRP plugin and the other for the Legacy Authentication. HTH see you !
Re: [firebird-support] gfix full or reserve required
Hi Helen. Thank you. I should pay more attention to the command usage. Hugo Eyng Em 06/07/2016 19:49, Helen Borrie hele...@iinet.net.au [firebird-support] escreveu: Thursday, July 7, 2016, 10:20:50 AM, Hugo Eyng wrote: > I tried to use gfix -w async -u USER -p PASSWAORD MYDB.FDB and gfix > displayed "full or reserve required". > What does it mean? That "full" or "reserve" is required? :)) The -u switch in gfix is NOT an abbreviated form for the username but for page-fill capacity, i.e., -u[se] with the argument reserve (for reserve space) or full (for use the full page). It's not what you want, I know, but don't set this to full unless the database is also read-only. Your password abbreviation is wrong for gfix, too. It is -pa[ssword]. The -p abbreviation in gfix is for something else, used in recovery of transactions from broken multi-database connections. You want: gfix -w async -user USER -password PASSWAORD MYDB.FDB Helen -- Atenciosamente, Hugo Eyng
Re: [firebird-support] Re: Simple create or alter procedure on Firebrid 3.0 creates "unsuccessful execution caused by system error that precludes successful execution of subsequent statements"
07.07.2016 9:57, jonatan.laurit...@yahoo.dk [firebird-support] wrote: > OK. After Firebird 64 bit installation it was necessary to make Firebird32 > bit client > installation and with Firebird 3.0 32bit fbclient.dll/gds32.dll this > statement can be > executed normally. Execution of statement must not be affected by client library bitness. At least not with such message. It seems that you used client library from different Firebird version or may be even from Interbase. You'd better to try to reproduce the problem with latest server snapshot and fill a ticket in bugtracker on success. -- WBR, SD. ++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
[firebird-support] Enable authorization for legacy Firebird clients
Hi, I don’t know if i have understand “Enable authorization for legacy Firebird clients” right but.. I just installed Firebird 3 to new development server and checked “Enable authorization for legacy Firebird clients” so I can test connection from old 2.5 clients. In this installation window I create random password like “pass1234”. When I connected to database from same server connection is okay with “pass1234”. But when I tried to connect from old development server where firebird 2.5 is installed with “pass1234” I get error “Your user name and password…”. My surprise was when I tried connect database from old server with pasword “masterkey” that connection is succesfully. I have not created user SYSDBA with “masterke” password and still I get connected in database. So my question is that should this be like this? Best regards, - Tomi
[firebird-support] Re: Clarification about 64bit and 32bit Firebird 3.0 software
07.07.2016 10:54, jonatan.laurit...@yahoo.dk wrote: > Are the following statements correct? > > - Most Firebird client software still is 32bit (Flamerobin, IBExpert, > Delphi 2009 and older editions) and therefore it requires 32bit Firebird > 3.0 client dlls (fbclient.dll or gds32.dll) even if it connects to the > 64bit edition of server. > > - 64bit Firebird server can receive connections both from 32bit and > 64bit clients. > > - Both 32bit and 64bit Firebird server uses the same ODS (physical) file > structure therefore DB.FDB created with 32bit server can be simply > copied and used on 64bit server and vice versa. Correct (given that "simply copied" implies stopping the FB server). Dmitry
[firebird-support] Re: Simple create or alter procedure on Firebrid 3.0 creates "unsuccessful execution caused by system error that precludes successful execution of subsequent statements"
OK. After Firebird 64 bit installation it was necessary to make Firebird32 bit client installation and with Firebird 3.0 32bit fbclient.dll/gds32.dll this statement can be executed normally.
[firebird-support] Clarification about 64bit and 32bit Firebird 3.0 software
Are the following statements correct? - Most Firebird client software still is 32bit (Flamerobin, IBExpert, Delphi 2009 and older editions) and therefore it requires 32bit Firebird 3.0 client dlls (fbclient.dll or gds32.dll) even if it connects to the 64bit edition of server. - 64bit Firebird server can receive connections both from 32bit and 64bit clients. - Both 32bit and 64bit Firebird server uses the same ODS (physical) file structure therefore DB.FDB created with 32bit server can be simply copied and used on 64bit server and vice versa. Jonatan
[firebird-support] Simple create or alter procedure on Firebrid 3.0 creates "unsuccessful execution caused by system error that precludes successful execution of subsequent statements"
Hi! I am trying to execute statement on Firebird 3.0 (64bit, Windows 10) from IBExpert (2016.5.2.1): create or alter procedure tests123 (p1 date, p2 date) returns ( p_test0 integer, p_test1 date) as begin end But there is immediate error: unsuccessful execution caused by system error that precludes successful execution of subsequent statements. Error reading data from connection. Connection will be closed immediately. If I remove p_test1 date argument, then command can be executed. I have sense, that Firebird does not like too much date arguments. The command can sometimes be executed from Flamerobin succesfully, but if command has failed in IBExpert, then command will also file in Flamerobin until Firebird service will be restarted. firebird.log has no entries about this failure. It is very strange behavior. Maybe it is Firebird bug? Or maybe IBExpert is doing something additionally that creates Firebird bug? Jonatan
