skerl /

* skerl
** Overview
=skerl= is a NIF wrapper around Skein hashing functions

** Quick Start
   You must have [[][Erlang/OTP R13B04]] or later and a GNU-style build
   system to compile and run =skerl=.

#+BEGIN_SRC shell
git clone git://
cd skerl

   Start up an Erlang shell with the path to =skerl= included.

#+BEGIN_SRC shell
cd path/to/skerl/ebin

   Hash a binary by calling =skerl:hash/2= with the desired number of
   bits for the resulting hash:

#+BEGIN_SRC erlang
1> Bits = 256.
2> Data = <<"foobarbazquux">>.
3> {ok, Hash} = skerl:hash(Bits, Data).
4> bit_size(Hash).

   You may find =skerl:hexhash/2= more useful, as it returns a
   hexadecimal-encoded string representing the hash:

#+BEGIN_SRC erlang
5> HexHash = skerl:hexhash(Bits, Data).      

** The Skein Hash

The underlying hashing code in Skerl is the reference implementation
of Skein from the official NIST submission.

Skein is a finalist candidate in the NIST competition to become SHA-3.

It is a hash function designed by 
Niels Ferguson, Stefan Lucks, Bruce Schneier, Doug Whiting, Mihir
Bellare, Tadayoshi Kohno, Jon Callas, and Jesse Walker.

Details on the algorithm as submitted and known analysis can be found
at ecrypt:

A full paper on Skein by the authors can be found at:

The official Skein page ( uses the headline:

Fast, Secure, Simple, Flexible, Efficient. And it rhymes with "rain."

** Contributing
   We encourage contributions to =skerl= from the community.

   1) Fork the =skerl= repository on [[][Github]].
   2) Clone your fork or add the remote if you already have a clone of
      the repository.
#+BEGIN_SRC shell
git clone
# or
git remote add mine
   3) Create a topic branch for your change.
#+BEGIN_SRC shell
git checkout -b some-topic-branch
   4) Make your change and commit. Use a clear and descriptive commit
      message, spanning multiple lines if detailed explanation is
   5) Push to your fork of the repository and then send a pull-request
      through Github.
#+BEGIN_SRC shell
git push mine some-topic-branch
   6) A Basho engineer or community maintainer will review your patch
      and merge it into the main repository or send you feedback.