Releases: sa6mwa/anystore
SetPersistence bugfix
This release fixes a bug in SetPersistence surfacing when path does not include one or more directories.
The Unstash step has been removed from EditThing for more flexibility. EditThing prompts the user to edit the underlying Thing interface directly. Other changes include improvements in documentation and examples.
Full Changelog: v0.4.0...v0.5.0
Remove lockfile on Close
Keeping the lockfile around when not using the store is less elegant than removing it when not needed. This release adds a Close function to the interface. In order to prevent a race condition in the store-code, the lockfile is re-created if it does not exist after acquiring the lock.
Full Changelog: v0.3.0...v0.4.0
Add HMAC-SHA256 data integrity
Version 0.3.0 introduces another breaking change by prepending the IV and cipher data with a HMAC-SHA256 hashing the IV and encrypted data using the same key used for the AES-CFB encryption. The HMAC is used to validate the message on decryption. Performance impact could not be measured in the benchmark tests and we gain better data integrity.
Full Changelog: v0.2.0...v0.3.0
Add gzip of persistence, NewStashReader
This is a breaking change from v0.1.0 regarding the Unstash function.
Persistence now has gzip support of gob-encoded data before encryption. There is also NewStashReader providing a means to access an io.Reader of a Stashed store (post-gzip, post-encryption, without reading a persistence file).
Full Changelog: v0.1.0...v0.2.0
First release of the AnyStore DB
The basic features of the AnyStore encrypted key/value DB.
Full Changelog: https://github.com/sa6mwa/anystore/commits/v0.1.0