0

We are using software that works on top of Firebird. It was all fine until work-from-home started. There where issues with firebird 2.5.x and connections that after some time people could not connect anymore. The software manufacture hint us that we should upgrade to 3.0 because of that. We migrate FDB to 3.0, and everything looks nice until clients start connecting (windows-dll) with 2.0 clients.

The issue is that when someone connect with older DLL version loaded they corrupt security3.fdb file and SYSDBA user is not found anymore, but the people that did login before works fine.

When using Flamerobin this result in error: isc_attach_database failed, sql message: -902, enfine code: 335544472 Your user name and password are not defined. Ask your database administrator to set up a Firebird login.

We do update clients versions of dll and this started to resolve the issue, but its been more than two weeks and I get early morning calls that people are unable to connect.

I'm using firebird3.0 from debian repo if that helps (because it use different default configuration than the one from firebird page).

The workaround that I find after many hours of looking thru the issue is replacing security3.fdb file while firebird is working and this works 80% in 20% I need to restart firebird after replacing file.

Is there a way to prevent this? I tried removing write permission on security file but firebird dont like that.

firebird.conf (the rest is on default aka commentout)

UdfAccess = Restrict /usr/lib/x86_64-linux-gnu/firebird/3.0/UDF   # the software use udf but without it it also lock down the database
RemoteServicePort = 3050  # just to be sure
RemoteBindAddress = 192.168.0.80 # this was needed because it would start listening on ipv6 only interface which was strange
Michal Sapsa
  • 52
  • 1
  • 6
  • 1
    May be : https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-compat-legacyauth.html – Val Marinov Apr 09 '20 at 07:41
  • I read that link, but something is not right. According it Srp don't relay on security3.fdb, yet that file was used. I reconfigured firebird with Legacy_Auth and see where we will go with that. Time will tell, if I wont have issue in next week I will be back to report it. – Michal Sapsa Apr 09 '20 at 18:59
  • Why do you think Srp doesn't use security3.fdb? Because it does, unless you have explicitly configured a different security database. Exactly which Firebird 3 version did you install? In any case, it might be better to ask your question on the firebird-support mailing list. – Mark Rotteveel Apr 10 '20 at 07:16
  • I used the one in debian repo: 3.0.5.33100.ds4-2, changing to using legacy_auth/legay_usermanager did not resolve the issue. – Michal Sapsa Apr 10 '20 at 07:21
  • 3.0.5.33100 is not a released version, but a snapshot development version, the Firebird 3.0.5 release is Firebird-3.0.5.33220-0, which is 120 builds after the version you're using. – Mark Rotteveel Apr 10 '20 at 07:27
  • this is the version provided by debian-repository. The issue was similar on official build to, so I would exclude development version as the issue. – Michal Sapsa Apr 24 '20 at 11:38

0 Answers0