CryptoGnome is an attempt to reinvent the wheel without reinventing the wheel. In other words, it appears to me that the combination of elements in rfc1945 (HTTP) and rfc1521 (MIME) can be very simply extended to provide the foundation of a network-oriented version control system. Security comes relatively cheaply from the use of https and the http native authentication framework.
Did I mention it is written in Scheme?
A stable (no guarantees of reliability or fitness for purpose) release is available via anonymous CVS at:
-r stable cryptognome
Cryptognome is currently a flat object repository. You can use Nutscrape as a client if you want, but you can't create new objects with it. I've got a brain-damaged client written for test purposes; its focus is on exercising the server, not being convenient for the developer.
I've listed the status on the 'Forge as
mostly due to the lack of features. However, from here on out
stability will be a high priority, as the CryptoGnome has
regressable core functionality. IOW, it's really alpha, but
The project diary more closely tracks the actual development work (which rambles around the bits I'm interested in at the moment), but there are certain things that I'm actively thinking about and consider essential to the project. In no particular order these are:
X-rsynccome to mind immediately); we may even be able to usefully introduce some cryptography hooks here.