Firebird high-level native client for Node.js / TypeScript updated to v0.0.1-beta.2 with a few changes:
Fixed crash after re-creating native client – #11
Moving to monorepo using lerna and yarn workspaces.
Fixed #2 – Throw an error when the client library is not loaded correctly.
Replace mocha and power-assert by jest.
Added appveyor.yml and build status.
Fix warning C4530 in Windows build.
Add node 10 to travis build matrix.
This webinar is devoted to memory usage in Firebird. In the first part of this webinar, we consider main memory types in operation systems, default distribution between them in Windows and Linux, and Firebird memory model.
If you’ve not seen usql before, it’s a universal command-line client for SQL databases , modeled on psql. usql makes it easy to work from the command-line, in a simple and consistent way across any database and on any platform (Windows, macOS, Linux). usql is written in Go, and provides things like syntax highlighting and compatibility with databases other than PostgreSQL
Here is the description for CVE-2017-11509
An authenticated remote attacker can execute arbitrary code in Firebird SQL
Server versions 2.5.7 and 3.0.2 by executing a malformed SQL statement. The
only known solution is to disable external UDF libraries from being loaded. In
order to achieve this, the default configuration has changed to UdfAccess=None.
This will prevent the fbudf module from being loaded, but may also break other
functionality relying on modules.
Read the new white paper “Authentication in Firebird” from IBPhoenix: Developments introduced in Firebird 3 provide many options for authenticating users attempting to attach to a database. No longer is authentication restricted to a single method: the methods available are determined by the plug-in authentication modules configured in the global and/or database config files.
Also, there are many interesting articles in Documentation area of IBPhoenix website.