[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
[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