Security fixes in Dbase32 1.3
Written for Dbase32 by Jason Gerard DeRose on 2014-09-29
In the C implementation, the reverse table is now rotated 42 bytes to the left so that all valid entries fit in a single 64-byte cache line, and likewise so that all valid entries are at least balanced between two 32-byte cache lines (16 entries are in each 32-byte cache line); note that although the C implementation of Dbase32 is now constant-time when validating or decoding a valid ID (on systems with a 64-byte or larger cache-line size), cache hits and misses can still leak information about what bytes are in an invalid ID.
For more details, please see:
http://