botan.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move the signature padding schemes to the PK operation classes,	lloyd	2015-03-23	1	-21/+6
\| \| \| \| \| \| \| \| \|	as was previously done with encrypt/decrypt ops. One feature dropped on the floor here is previously PK_Signer by default did verification of signatures before releasing them as an measure against fault attacks. However in addition to being expensive this turned out to be difficult to implement with the new scheme.
*	In PK encrypt/decrypt move pad calls to the operation. This allows an	lloyd	2015-03-14	1	-4/+1
\| \| \| \| \| \| \| \| \|	op to use a padding scheme outside of our knowledge or control, for instance an OpenSSL RSA op which uses OpenSSL's padding code. Similar change for key agreement and KDFs for the same reason. Add an EME_Raw type; previously this operation was implicit in the code in pubkey.cpp
*	Add new module `ffi` which provides a plain C interface, plus a new	lloyd	2015-02-16	1	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \|	ctypes Python wrapper that uses it. The API is intentionally designed to have a very simple ABI (extern "C", all structs are opaque, no memory ownership passing the FFI boundary, limited set of simple types as args) so the ctypes wrapper is quite simple. Currently ffi provides ciphers, hashes, MACs, RNGs, PBKDF, KDF, bcrypt, and most public key operations. Remove the old boost.python wrapper and all the build code for it.
*	Ensure all files have copyright and license info.	lloyd	2015-01-10	1	-1/+1
\| \| \| \| \|	Update license header line to specify the terms and refer to the file, neither of which it included before.
*	Guess I won't be needing these	lloyd	2014-01-18	1	-1/+0
\|
*	unique_ptr all the things	lloyd	2014-01-18	1	-39/+15
\|
*	Move lib into src	lloyd	2014-01-10	1	-0/+461