ksql version feed

0.3.5

2018-12-28T00:00:00Z

Fix which functions are deprecated. The bind functions are not—the stmt functions (which return data without checking type) are. No functional change.

Sync with latest oconfigure and test compiling on Linux (musl, glibc), FreeBSD, and of course the origin system OpenBSD. No functional change.

0.3.4

2018-12-17T00:00:00Z

Complete musl work, at least with musl-gcc on Debian. Finally mark unsafe functions as being deprecated.

0.3.3

2018-12-16T00:00:00Z

Build compatibility with musl and sync with newest oconfigure. No code change beyond that.

0.3.2

2018-05-09T00:00:00Z

Add the ksql_result_double(3) family of functions. These will replace the existing ksql_stmt_double(3) family with safe versions. Specifically, the functions return an error code (if not exiting with errors) that check for null values and columns outside of the result range.

0.3.1

2018-04-26T00:00:00Z

Make sure that one cannot bind a parameter to an invalid index. These now cause the bind functions (see ksql_bind_double(3) and friends) to return KSQL_BINDPARAM.

API change: have ksql_trace(3) and ksql_untrace(3) return proper error codes.

Document pledge(2) promises in ksql(3).

A nice fix due to issues/7 as investigated by schwarze@: allow running without /dev/null at all. Yay!

The fixes in this release were implemented or suggested by Ingo Schwarze (schwarze@) in an audit generously funded by CAPEM Solutions, Inc. Thank you so much!

0.3.0

2018-03-21T00:00:00Z

Minor release bump: this is because I've added a new field to struct ksqlrole to specify whether a role is allowed to run ksql_open(3). This plugs a hole of arbitrary roles being able to close out the database, then open another one.

Merge documentation and error-path patches by cornett—thank you!

The remaining fixes in this release were implemented or suggested by Ingo Schwarze (schwarze@) in an audit generously funded by CAPEM Solutions, Inc. Thank you so much!

Mention correct headers (erring on the side of caution) in documentation.

Have security issues (e.g., transition to a disallowed role) result in a log message directly to stderr and terminating the application. Earlier, there was no log message.

Fix up the ksql_lastid(3) function and manpage to handle boundary conditions and include an example.

API change: earlier, ksql_open(3) would close out existing databases before opening. Now it errors out, requiring the caller to close the database manually. Also, add a field to struct ksqlrole that inhibits a role's ability to open a database.

When binding blobs or text, the application now internally copies the buffer. This allows callers to discard the memory buffer immediately after binding it, without needing to wait until the statement is finalised.

0.2.5

2018-03-09T00:00:00Z

Fix a memory leak in ksql_open(3) if the system spins on a failed opening of the database. Also fix a possible error when closing the database fails, then a log message follows that might re-invoke the closed database.

The fixes in this release were implemented or suggested by Ingo Schwarze (schwarze@) in an audit generously funded by CAPEM Solutions, Inc. Thank you so much!

0.2.4

2018-02-01T00:00:00Z

Back out debugging code accidentally left in release version. No change to functionality except an error message on stderr.

Also use abort instead of assert for run-time failures in roles or statements.

0.2.3

2018-01-31T00:00:00Z

Show atom feed. No functional change to any code or documentation.

0.2.2

2018-01-30T00:00:00Z

Add full RBAC capability. (Still somewhat experimental…) See ksql_role(3) and ksql_cfg_defaults(3) for details.

0.2.1

2018-01-25T00:00:00Z

Fix installed manpages. Move the check of stored statements (see ksql_cfg_defaults(3)) into the child process of split processes. This ensures that protection occurs outside of the area of influence of the caller.