Stegosaur is intended to be a small, fast, secure datastore for any type of data. Items inserted into this datastore can be hidden steganographically such that it is impossible not only to read them but also even to prove that they exist without the correct key. It should be possible to create a "decoy" key which unlocks only innocuous items, with more sensitive items requiring a different key. This way, if coerced into surrendering a key, a Stegosaur user could volunteer the "decoy" key while plausibly denying that any other keys exist, thereby keeping the sensitive data secure from prying eyes.

Stegosaur itself will merely be an engine which developers can then use to build applications. (A very small example application will be included). The initial 1.0 release will be quite modest in terms of features:

The ability to create an arbitrarily-sized datastore on disk into which items can be inserted, encrypted, and hidden steganographically. However the datastore itself will not be mountable as an actual file system (as compared to StegFS). The ability to "tag" items with descriptive labels and do simple queries to find them. However, this will not be a fully ACID compliant SQL database engine (as compared to, say, MySQL). Single-client access only... the initial release will only allow a datastore to be open by one client at a time. Future versions may address the above limitations.

Stegosaur is currently in planning/design, with no fixed date for the 1.0 release. Updates will be posted to K5.

Rough project plan:

0.1.0 : Ability to create and format blank volumes 0.2.0 : Ability to add blank layers and nested layers 0.3.0 : Ability to insert items 0.4.0 : Ability to tag items 0.5.0 : Ability to query items 0.6.0 : Simple demo application 0.7.0 : Code review, performance enhancements, general refactoring 1.0.0 : Functional release