resilar

CMake is an overkill for compiling three portable `.c` files when simple `cc *.c -o crchack` suffices. Maybe later if we decide to build a dynamic library (#7).

A major interface overhaul is coming soon in order to add support for streaming CRC calculation (#5) and a more efficient forging algorithm (#2). Let's consider splitting crchack into a...

We could use [Nayuki's method](https://www.nayuki.io/page/forcing-a-files-crc-to-any-value) with loss of generality. But first, let's try to speed up the CRC function with precomputed tables because the cost of forging is roughly _b_...

The cost of forging has been reduced to **O**(n + b w³ *log* n) by exploiting **O**(w³ *log* n)-time sparse CRC calculation for b messages consisting of n-1 zeros and...

+1, this would allow a safe zero-copy implementation of my [makeuniq.rs](https://gist.github.com/resilar/925ea268d9e15e79fb9cbfd5ab9d2d79) script.

Ideas for fixing the issue: 1. Add missing shared-cache locking (`setSharedCacheTableLock()` and Btree locks?) 2. Read the database page 1 with a novel method * Consider low-level file locks &...

Accidental close. Reopening. --- Also quick note about the suggested fix (1) which may feel like the obvious solution. I'd argue that is not necessarily the case because the current...

I agree that the current behavior is non-ideal. A better approach is to return an error and prevent accessing encrypted databases if entropy generation fails. Maybe also spam error messages...

Sorry about the accidental close... My initial reaction was that adding a C API for accessing the salt would be unjustified because it is so rare operation. Moreover, competent people...

Commit 3d2c17b adds raw keys and support for specifying a salt. I'm leaving this issue open until we implement a way to read the salt (be it a C function...