[#CORE-6050] When FB 3 fbclient.dll connects to a remote FB 2.5 server, it tries to open local (client-side) directories and files

Firebird Core

When FB 3 fbclient.dll connects to a remote FB 2.5 server, it tries to open local (client-side) directories and files

Created: 17/Apr/19 07:38 AM Updated: 02/May/19 07:30 AM

Component/s:

API / Client Library

Affects Version/s:

3.0.4

Fix Version/s:

3.0.5, 4.0 Beta 2

File Attachments:

None

Image Attachments:

1. ProcessMonitorLog.png
(22 kB)

Environment:

Windows 10, FB 2.5.8, fbclient.dll 3.0.4

QA Status:

Cannot be tested

Description

« Hide

When FB 3 fbclient.dll connects to a remote FB 2.5 server, it tries to open local (client-side) directories and files.

isql -user sysdba -password masterkey remotehost/3050:D:\Test.FDB

ProcessMonitor run on the client side reveals that isql attempts to read local (client-side) files and directories ("D:\Test.FDB" in this case). The remote connection is then successfully established, but if the client-side drive is a specific type (internal card reader etc.), the affected application may fail with an error message "There Is No Disk in the Drive. Please Insert a Disk into Drive \Device\harddisk1\Dr1".

All

Comments

Change History

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

michalk1 added a comment - 23/Apr/19 06:08 AM

I confirm that in current snapshot build 3.0.5.33122 the client-side reads are gone. Thanks for the quick fix.

[ Permalink | « Hide ]

Alexander Peshkov added a comment - 18/Apr/19 03:34 PM

Please try tomorrow snapshot - should be fixed.

[ Permalink | « Hide ]

michalk1 added a comment - 18/Apr/19 06:44 AM

I didn't check it on Linux, the problem may be Windows specific. So far I found no workaround. I tested also the new UNC connection syntax (inet://) , but those strange client-side directory scans are still present. It is like the fbclient at some point tries to fall into local embedded mode, although it is clearly instructed by the TCP connection string that the directory is ment for server. Needless to say, however, that this doesn't happen when connecting FB 2.5 client to FB 2.5 server, or FB 3.0 client to FB 3.0 server.