anchor.diff:  ~~~~~~~~~~~~~~
   
   Buddy differs with other libraries because it takes very different approach for handling
  -authentication. In first step, it clearly split authentication and authorization in two
  -separated steps and in second step, implements it using "backends" and protocols for easy
  +authentication. Firstly, it clearly split authentication and authorization in two
  +separate steps. Secondly, it implements it using "backends" and protocols for easy
   extensibility.
   
   If you are not happy with builtin backends, you can implement your own and use it with
  
positive.code: *Buddy is a security library/framework?*
  
  Yes and No. I don't like call "security" library because security represents a very generic
  concepts and can contain a lot of things. Buddy is target to cryptography, message signing
  and authentication/authorization extensions for ring compatible web applications. You can see
  the main target on the "Introduction" section of this documentation.
  
  
negative.code: | OFB               | `:ofb`
  |========================================
  
  Encrypting data using buddy's crypto primitives is almost as easy. In case of block ciphers, you
  should know the block cipher and cipher mode you want to use.
  
  NOTE: currently buddy comes with limited number of ciphers and modes, but in near future
  more many more options should be added.
  
  .Example encrypt
  [source, clojure]
  