Add in RandomNonceBox implementation

This class implements a strategy for nonce generation and transport,
that of randomly generating 24 bytes and then prepending them to the
ciphertext.  To decrypt, the reverse operation is called.
Make docs/constants consistent for RandomNonceBox

This is mostly making sure we use same named constant, etc.
Add specs for the RandomNonceBox

Which did actually catch a very important error: The box method was
returning the plain text (!).  Otherwise, they mostly check things like
round tripping.
Try and solve the encoding errors on rbx-19

Make sure we have 8-bit zeros.
Merge pull request #24 from cryptosphere/random_nonce_box

Add in RandomNonceBox implementation
Dragons belong at the edges of the map

Moving the Scalar documentation down to the bottom of the README.
Documentation on Hashes and Authenticators is likely to be more
interesting to a lot of users of the library.
Document the Hash module

The library is now about 80% documented, according to YARD's stats.
Mostly its the NaCl constants pulling it down.
Document CryptoError
Mark NaCl module as private

Really, it's just for hanging constants and method bindings off.
Box usage notes
Updated typo 'recieving' to 'receiving' in README.md

Found a little typo.
Merge pull request #26 from theDoug/patch-1

Updated typo 'recieving' to 'receiving' in README.md
Document the inspect methods
Document Auth namespace

Now 97% doc'd in yard
Document version

98%
Changes to verify functions

Raising versions renamed to bang methods, non-raising ones replace them
Specs for key equality and lexicographical sorting

A shared example group that should cover most of the cases for both
equality and sorting.
Implement key comparison

Closes #27

Keys (Public, Private, Signing, Verify) can now be checked for equality
and also compared lexicographically.  In addition, the check for
equality is done in constant time.  But I'm not sure if the way the
checks are done means we leak anyway.  Perhaps its best to define
equality specifically anyway...
Paranoia equality

Because I don't know quite how <=> and Comparable interact to define ==.
So err on the side of safety, by explicitly defining it
Merge pull request #28 from cryptosphere/dev/compare

Implement Key Comparison