News and announcements

armhf, arm64 builds now available in stable PPA

Written for Dbase32 by Jason Gerard DeRose on 2016-05-29

Starting with Dbase32 1.7, the stable releases PPA now has builds for armhf and arm64!

https://launchpad.net/~novacut/+archive/ubuntu/stable/+packages

Thanks to the Launchpad developers for enabling this feature!

For more details on the Dbase32 1.7 release, please see:

https://launchpad.net/dbase32/trunk/1.7

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://docs.novacut.com/dbase32/security.html

And see:
http://docs.novacut.com/dbase32/changelog.html

Read more

Security fixes in Dbase32 1.2

Written for Dbase32 by Jason Gerard DeRose on 2014-08-31

Dbase32 1.2 mitigates the effectiveness of timing attacks against `db32dec()` and `check_db32()`.

These improvements make it much more difficult for an attacker to gain insight into secret data that is either Dbase32 encoding itself or merely interacts with other Dbase32 encoded data. All users are strongly encouraged to upgrade.

For more details, please see:
https://bugs.launchpad.net/dbase32/+bug/1359828

Read more

Dbase32 1.0 released!

Written for Dbase32 by Jason Gerard DeRose on 2014-03-22

Dbase32 1.0 has been released, with a stable API with which we'll maintain indefinite backward compatibility:

    http://docs.novacut.com/dbase32/dbase32.html

There was an API change from 0.10 to 1.0: the `log_id()` function has been renamed to `time_id()`.

However, for backward compatibility `dbase32.log_id` is an alias for `dbase32.time_id()`. So existing software should not required any code change to use Dbase32 1.0.

Although the `log_id` alias should be around for a good long while, please don't count on it being around forever.

`log_id()` never felt quite right to me as a name, but it took me quite a while to decide what would be better.

I also added some documentation on security issues, on how you can use the Dbase32 validation functions to quickly sanitize untrusted input:

    http://docs.novacut.com/dbase32/dbase32.html#security

15 of 6 results