Starting to change the Kingslayer interface to accept a parameters hash
Changed to the kingslayer constructor to accept a params hash
some rearrangements to kingslayer spec
Added initialization tests to KS and changed the constructor to accept either a password and an init number OR an init_key. However, so far this init key does nothing
New constructor setting password to given key, or generates a random key using opensll if no password is given
checking init_key format for 256 hex string
Better tests for init_key
Big checking. Finished KS reorg. removed init_key option, only password and optionally also iter. If password is 64 long hex string we set iter to 1 in constructor. When CC encrypts we only use the empty constructor which generates a random key. If you selected a password that is 64 long hex (even with low entropy) KS will not stretch it. Also password is now saved as a file to the private directory and read from there instead of using a cookie. Removed my own password generator
Removed one more curely q from KS. If instantiated with a password, we set to the given iterations if those are given, otherwise we generate a random key and use one iteration. It is then upto the crypto helper upon decryption to try first to decrypt with one iteration to catch the random key case, and otherwise try to decrypt with iterations, not worrying at all about the format of the key