Issue Details (XML | Word | Printable)

Key: CORE-6307
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Luciano Mendes
Votes: 0
Watchers: 2

If you were logged in you would be able to see more operations.
Firebird Core

Unable to disable embedded connections following the Firebird 3.0 Quick Start Guide

Created: 17/May/20 02:51 PM   Updated: 18/May/20 04:51 PM
Component/s: Engine
Affects Version/s: 3.0.5
Fix Version/s: None

File Attachments: None
Image Attachments:

(3 kB)
Windows 10 x64
Firebird 3.0.5 (x64)

QA Status: No test

 Description  « Hide
According to the Firebird 3.0 Quick Start Guide ( to disable embedded connections you need to define the following list of providers on firebird.conf file:

Providers = Remote,Loopback

instead of the default value:

Providers = Remote,Engine12,Loopback

but after remove the Engine12 from the list of the providers the following error message is displayed when it tried to connect with a existing database (e.g.: LOCALHOST:CHRONOS_CIN):

- 335545106 - Error occurred during login, please check server firebird.log for details

THUNDERBOY Sun May 17 11:19:07 2020
Authentication error
unavailable database


AuthClient = Legacy_Auth, Srp, Win_Sspi
AuthServer = Legacy_Auth, Srp, Win_Sspi
ServerMode = Super
UserManager = Legacy_UserManager, Srp
WireCrypt = Enabled
Providers = Remote,Loopback
DefaultDbCachePages = 30K
FileSystemCacheThreshold = 2M
LockHashSlots = 30011
LockMemSize = 15M
RemoteServicePort = 3050
TempBlockSize = 2M
TempCacheLimit = 3000M
SecurityDatabase = $(dir_secDb)/security3.fdb

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Alexander Peshkov added a comment - 18/May/20 06:38 AM
Suggested method
 Providers = Remote,Loopback
obviously works only on client, on server it should not be used.

The best way is to correctly assign access rights to database files - they should be accessible only to firebird server, not to users, connecting to databases locally. Also one can use xnet:// prefix before database name.

Karol Bieniaszewski added a comment - 18/May/20 04:51 PM
You can also use on connect trigger and prohibit there some protocols
Current protocol you can read by: