Security
Summary of Changes
Better password encryption
A. Peshkov

Password encryption/decryption now uses a more secure password hash
calculation algorithm.

Users can modify their own
passwords A. Peshkov
Users can now modify their own passwords.
Remote access to security database is
rejected A. Peshkov

The server now rejects access to security.fdb through any remote protocol.
GSEC now uses the Services API A. Peshkov
Protection from brute-force attack A. Peshkov
Attempts to get access to the server using brute-force techniques on accounts
and passwords are now detected and locked out.
API Vulnerabilities closed C. Valderrama,
A. Peshkov
Several known vulnerabilities in the API have been closed. More information
to come.
Details of the Security
Changes in Firebird 2.0 A. Peshkov
Several changes have been implemented to improve security. Aspects that have
received special attention include:
the lack of brute-force resistant passwords encryption in the security
database
l
the ability for any remote user with a valid account to open the security
database and read hashes from it (especially interesting in combination
with the first point)
l
l the inability for users to change their own passwords
the lack of protection against remote brute-forcing of passwords on the
server directly
l
Firebird 1.5 Authentication

Nasıl bir güzelliği? Password'lerin şifrelenmesini mi?
Bu adamlar şifreleme için SHA-1 algoritması kullanmış, geçenlerde bu algoritma kırıldı. Ee? Ne olacak?

# ----------------------------
# In-memory sorting module
#
# The amount of memory allocated for each sort block.
#
# Type: integer
#
#SortMemBlockSize = 1048576

#
# The maximum amount of memory to be allocated by the in-memory
# sorting module.
#
# For Classic servers, this setting is defaulted to 8 MB.
# Although it can be increased, the value applies to each client
# connection/server instance and thus consumes a lot of memory.
#
# Type: integer
#
#SortMemUpperLimit = 67108864

# ----------------------------
# Locking and shared memory parameters
#
# Bytes of shared memory allocated for lock manager.
# In Classic mode, the size given is used for the initial allocation. The
# table expands dynamically up to the limit of memory. In SuperServer, the
# initial size is also the final size.
# Default is 96K on Linux and Solaris, 256K on Windows.
#
# Type: integer
#
#LockMemSize = 262144

# ----------------------------
#
# Bytes of shared memory allocated for event manager.
#
# Type: integer
#
#EventMemSize = 65536

Nasıl bir güzellik bekliyordun merak ettim de sordum. Hala söylemedin @csyasar

# ----------------------------
# Number of cached database pages
#
# This sets the number of pages from any one database that can be held
# in cache at once. If you increase this value, the engine will
# allocate more pages to the cache for every database. By default, the
# SuperServer allocates 2048 pages for each database and the classic
# allocates 75 pages per client connection per database.
#
# Type: integer
#
#DefaultDbCachePages = 2048

the amount of physical RAM (as little as 16MB will do for a start)