I’ve started implementing Digital Signature support in EzCrypto. It is pretty early stage yet but my proof of concept unit tests are working.
The aim is to have 2 easy to use classses:
They both will have a few simple static methods like in EzCrypto for generation and loading of Private/Public keys. Otherwise Signer has a sign(data) method and Verifier a verify(sig,data) method. All the other stuff such as certificates and whatever I aim to hide within the code.
A sample of code would be:
signer=EzCrypto::Signer.from_file "testsigner.pem"
sig=signer.sign "I promise to obey this"
verifier=signer.verifier
assert sig.verify sig, "I promise to obey this"Keep an eye on this space for more.
I just released EzCrypto 0.5. It’s available as a ruby gem, just type gem install ezcrypto to install it.
From a user standpoint there really shouldn’t be much difference as I’ve been pretty strict on keeping the api the same. However the internals of ActiveCrypto have had some pretty heavy refactoring to make some things cleaner in preparation for the up and coming release of the act_as_capability Rails plugin.
There is nothing there yet as I am learning about generators right now. I will probably start checking things into svn when I get back from a couple of days vacation to Las Perlas (of Survivor fame).
This plugin is extracted from WideWord and will allow you to create your own Secure URL (Capability in security researcher parlance) based services in Rails just like WideWord and WideBlog.