"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "builds/install/misc/firebird.conf.in" between
Firebird-3.0.2.32703-0.tar.bz2 and Firebird-3.0.4.33054-0.tar.bz2

About: Firebird is a relational database offering many ANSI SQL standard features.

firebird.conf.in  (Firebird-3.0.2.32703-0.tar.bz2):firebird.conf.in  (Firebird-3.0.4.33054-0.tar.bz2)
skipping to change at line 54 skipping to change at line 54
# Strings are also what they sound like, strings. Examples: # Strings are also what they sound like, strings. Examples:
# RemoteServiceName = gds_db # RemoteServiceName = gds_db
# RemotePipeName = pipe47 # RemotePipeName = pipe47
# #
# Scopes # Scopes
# ------ # ------
# Some parameters are marked as per-database / per-connection configurable. # Some parameters are marked as per-database / per-connection configurable.
# Per-database configuration is done in file databases.conf (former aliases.conf ). # Per-database configuration is done in file databases.conf (former aliases.conf ).
# Per-connection configuration is primarily client tool and done using # Per-connection configuration is primarily client tool and done using
# isc_dpb_config parameter in DPB (isc_spb_config for services). # isc_dpb_config parameter in DPB (isc_spb_config for services).
# Notice that per-database entries also may be tuned using DPB in case of # Configuration data, added to parameters block, has same format as this file.
# embedded engine when attaching to database first time. # Pay attention that since firebird3 there is no hard limit of 255 bytes per ent
ry
# provided you are using isc_dpb_version2 format of DPB. The simplest way to cre
ate
# DPB/SPB is to use IXpbBuilder - when needed you will have >255 bytes entries i
n
# parameters block. Notice that per-database entries also may be tuned using DPB
# in case of embedded engine when attaching to database first time.
# #
# Macro substitution # Macro substitution
# ------------------ # ------------------
# There is a number of predefined macro commands, that can be used in config # There is a number of predefined macro commands, that can be used in config
# files where directory name is needed. They are available using $(name) syntax. # files where directory name is needed. They are available using $(name) syntax.
# The complete list of them as follows: # The complete list of them as follows:
# root - root directory of firebird instance # root - root directory of firebird instance
# install - directory where firebird is installed # install - directory where firebird is installed
# this - directory where current configuration file is located # this - directory where current configuration file is located
# dir_conf - directory where firebird.conf and databases.conf are located # dir_conf - directory where firebird.conf and databases.conf are located
skipping to change at line 385 skipping to change at line 389
# ---------------------------- # ----------------------------
# #
# This group of parameters determines what plugins will be used by firebird. # This group of parameters determines what plugins will be used by firebird.
# Format of string is the list of plugins, separated by space, ',' or ';'. # Format of string is the list of plugins, separated by space, ',' or ';'.
# Plugins will be tried in an order, specified here. # Plugins will be tried in an order, specified here.
# In many cases correct order is important! # In many cases correct order is important!
# #
# Type: string # Type: string
# AuthServer and AuthClient determine what authentication methods will be used # AuthServer and AuthClient determine which authentication methods will be used
# by network server and client redirector. Secure remote passwords plugin # by network server and client redirector. The Secure remote password plugin
# is default one. Except configured by default SRP plugin firebird also has # using SHA-1 for the client proof is the default for both client and server.
# Legacy_Auth plugin which is used to emulate pre-FB3 login protocol making it # Additionally, the default client configuration (AuthClient) also supports new
# possible for client to talk to old servers and for server to listen to request Srp256
s # plugin using SHA-2 for the client proof. This enables backwards compatibility
# from old clients. Legacy_Auth is VERY unsecure. On windows Win_Sspi plugin may # with older Firebird 3 servers & clients but in order to meet NIST requirements
# be also used - it implements windows trusted authentication and backward # Srp256 should be used. To enforce NIST requirements on your server set
# AuthServer=Srp256. Be aware that this breaks compatibility with older
# than 3.0.4 clients.
#
# The default client configuration (AuthClient) also supports the pre-Firebird 3
legacy
# authentication protocol (Legacy_Auth). This is again for backwards
# compatibility but has many known weaknesses and is deprecated for current use.
#
# The default Windows client configuration (AuthClient) also includes support fo
r
# the Win_Sspi plugin. This implements windows trusted authentication and is bac
kward
# compatible with 2.1 and 2.5 clients and servers running on windows. # compatible with 2.1 and 2.5 clients and servers running on windows.
# #
# Per-database configurable. # Per-database configurable.
# #
#AuthServer = Srp #AuthServer = Srp
# #
# Per-connection and per-database configurable. # Per-connection and per-database configurable.
# #
#AuthClient = Srp, Win_Sspi, Legacy_Auth #AuthClient = Srp, Srp256, Legacy_Auth #Non Windows clients
#AuthClient = Srp, Srp256, Win_Sspi, Legacy_Auth #Windows clients
# #
# If you need to use server plugins that do not provide encryption key (both Leg acy_Auth # If you need to use server plugins that do not provide encryption key (both Leg acy_Auth
# & Win_Sspi) you should also turn off required encryption on the wire with Wire Crypt # & Win_Sspi) you should also turn off required encryption on the wire with Wire Crypt
# configuration parameter except when working with the XNET protocol which is ne ver encrypted. # configuration parameter except when working with the XNET protocol which is ne ver encrypted.
# #
# UserManager sets plugin used to work with security database. If more than # UserManager sets plugin used to work with security database. If more than
# one plugin is given, first plugin from the list is used by default. If you # one plugin is given, first plugin from the list is used by default. If you
# need to manage legacy logins using legacy tools set it to Legacy_UserManager. # need to manage legacy logins using legacy tools set it to Legacy_UserManager.
# Other managers may be chosen in create/alter/drop user commands. # Other managers may be chosen in create/alter/drop user commands.
 End of changes. 3 change blocks. 
11 lines changed or deleted 31 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)