anchor.diff:  
   The "signing framework" of _buddy_ is mainly based on django's
   link:https://docs.djangoproject.com/en/1.6/topics/signing/[Cryptographic
  -signing] library but extended with various signing algorithms.
  +signing] library but extended with various signing algorithms and cryptography
  +support.
   
   It can be used for several purposes:
   
  +- Safety send/store signed or encrypted messages.
   - Safely storing session data in cookies instead of a database (It prevents others from changing session content)
   - Self contained token generation for use it on completely stateless token based authentication.
   
  
positive.code: 3. handle-unauthorized is executed of your backend, if user has specified it own function,
     the user defined function is executed else, default behavior is executed.
  
  Core library
  ------------
  
  Behind the scenes, _buddy_ uses an internal library exposed in the
  `buddy.core` namespace.  There are more low level functions here for
  hash, hmac, sign and coding that are used by other parts of _buddy_.
  
  Cryptographic hash algorithms
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  All hash algorithms interface is located on the `buddy.core.hash` namespace.
  
  Available hash algorithms:
  
  - *sha256*
  - *sha384*
  - *sha512*
  - *sha1*
  - *md5*
  
  Basic usage
  ^^^^^^^^^^^
  
negative.code: buddy documentation
  ===================
  Andrey Antukh, <niwi@niwi.be>
  0.1.2, 2014-04-07
  
  :toc:
  :numbered:
  