cloud-email/cryptography - python cryptography

	Commit message (Collapse)	Author	Age	Files	Lines
*	remove maccontext (#4803)	Paul Kehrer	2019-03-07	1	-2/+1
\|
*	Simplify string formatting (#4757)	Alex Gaynor	2019-02-20	1	-1/+1
\|
*	support byteslike in hmac update (#4705)	Paul Kehrer	2019-01-17	1	-1/+2
\| \| \|	needed for some KDF keying material
*	support bytes-like keys in CMAC and HMAC contexts (#4701)	Paul Kehrer	2019-01-16	1	-1/+2
\|
*	create & use _evp_md_from_algorithm and _evp_md_non_null_from_algorithm (#4542)	Paul Kehrer	2018-10-29	1	-3/+3
\| \| \| \| \| \|	* create & use _evp_md_from_algorithm and _evp_md_non_null_from_algorithm * remove unused import
*	add blake2b/blake2s support for hmac (#3873)	Paul Kehrer	2017-08-22	1	-4/+3
\| \| \| \| \| \| \| \| \| \|	* add blake2b/blake2s support for hmac This was a bug, but it turns out the noise protocol suggests using the HMAC construction with BLAKE2 (rather than BLAKE2's own keyed functionality) for a few reasons, so we should support it. * actually test the thing
*	move MACContext to mac.py and eliminate interfaces.py (#3631)	Paul Kehrer	2017-05-29	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \|	* move MACContext to mac.py and eliminate interfaces.py finally * improve title * re-add and deprecate interfaces.MACContext * use pytest.warns instead of deprecated_call The pytest docs insist that deprecation warnings are handled differently and that you should use deprecated_call, but this works so okay then
*	Removed 0.9.8 specific hmac code (#2995)	Alex Gaynor	2016-06-19	1	-10/+4
\|
*	opaque HMAC_CTX, which requires some helper functions	Paul Kehrer	2016-03-09	1	-7/+6
\|
*	converted a few more asserts	Alex Gaynor	2015-09-26	1	-1/+1
\|
*	convert the rest of the openssl backend to using openssl_assert	Paul Kehrer	2015-09-25	1	-4/+4
\|
*	move hash interfaces	Paul Kehrer	2015-02-13	1	-2/+2
\|
*	Update the license header for every source file, as well as the documentation.	Alex Gaynor	2014-11-16	1	-12/+3
\| \| \| \|	Fixes #1209
*	Move the cryptography package into a src/ subdirectory	Donald Stufft	2014-11-13	1	-0/+90
	Due to differences in how py.test determines which module to ``import`` the test suite actually runs against the cryptography which is in the current directory instead of the cryptography which is installed. The problem essentially boils down to when there is a tests/__init__.py then py.test adds the current directory to the front of the sys.path, causing it to take precedence over the installed location. This means that running the tests relies on the implicit compile that CFFI does instead of testing against what people will actually be runnning, which is the module compiled by setup.py.