introduce MacHelper interface and clean-up API

* there's no need to have a RandomSource within the MacHelper
overwork MAC subsystem

* now it's modular
* add some sample mac implementations
* test mac performance
let helpers tell the needed keysize; improve debug output

* now the crypto helper have a method "keySize" that can be
  used to gather the needed key size
* toString was implemented to improve debug output, esp.
  the used crypto-helpers should be noted
* remove RandomSource#generateByte as we are mostly using
  this with byte-arrays
add an initial Changelog
update Changelog
update readme.md with performance numbers
move documentation into docs/
Add more algorithms to PerformanceTest
bump pom.xml Version to 0.1
update Changelog for Version 0.1
bump version to 0.2-wip
drop support for java 1.6/java6se

According to Wikipedia[0] Java SE 6 was released in December 2006 and
reached end-of-life in February 2013. Since then multiple security
vulnerabilities were fixed but those fixes are not available publicly.
As we are writing security-related software this is a no-go.

In addition parts of our toolchain (findbugs) are not working with
Java6 anymore.

This drops support for Java6, Java7 and 8 are supported as usual. I
will not add patches that were written just for the sake of utilizing
Java7+ features but won't decline patches that are using Java7-Features.

At least the travisci build will now finish successfully.

[0] http://en.wikipedia.org/wiki/Java_version_history
Merge branch 'master' of github.com:Archistar/archistar-smc
add PerformanceTest output for archistar 0.11

While the data block size seems to be rather irrelevant, the java
version seems to be highly important.

Java 8 seems to be roughly 89% *slower* than Java7 for now.
Change PerformanceTest data block sizes

So far we have thrown in a couple of data block sizes without giving
the selection much thought. Performance was rather similar, we need
multiple block sizes to find out about possible regressions.

To limit processing time I've limited our tests to 4 block sizes:

 *    4kB -- block size for harddrives and SSDs
 *  128kB -- ``small'' documents, notes, emails
 *  512kB -- ``larger'' documents, images
 * 4096kB -- high-quality images, audio
Cevallo should follow the style of other Algorithms

This will allow testing Cevallo with other encryption schemes
than ShamirPSS.
restructure code and introduce CryptoEngine

The algorithms are now split between at.archistar.crypto.secretsharing
and at.archistar.crypto.informationchecking. As it gets tedious to
configure the algorithms a new interface CryptoEngine was added. The
basic idea is that end-users are just instantiating a CryptoEngine and
the cryptoengines themselve configure all needed compontents (like
symmetric encryption algorithms, secret-sharing, rng,
information-checking, decoder). This resembles Spring a little bit.

Let's start with an RabinBenOrEngine and a CevalloEngine.
Merge remote-tracking branch 'upstream/master'