From 560874f4b8711897ea644b8f5817113e7221dbec Mon Sep 17 00:00:00 2001 From: Thorsten Behrens Date: Sun, 2 Jan 2011 03:24:57 -0500 Subject: Update documentation with current state of security of hash and cipher functions. Update documentation with Python 3.x notes. --- python-3-changes.txt | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) (limited to 'python-3-changes.txt') diff --git a/python-3-changes.txt b/python-3-changes.txt index 687396f..880405b 100644 --- a/python-3-changes.txt +++ b/python-3-changes.txt @@ -100,16 +100,7 @@ TODO: correct. While at it, ensure that functions observe the guidelines below re type. This is friendlier than just relying on Python's errors. -- Document the expected types for functions. - The cipher, the key and the input texts are byte-strings. - Plaintext decodes are byte-strings. (?? Not true for all functions ??) - In keeping with how Python 3.x's hash functions work, the input MODE is a - text string. - hexdigest() returns a text string - digest() returns a byte-string. -- Need additional unit tests for Protocol/AllOrNothing, PublicKey/ElGamal, - random/random +- Need additional unit tests for Protocol/AllOrNothing - Make sure DerSequence slicing is tested, since I took the explicit slice functions away in 3.x -- PublicKey/qNEW will not be unit-tested. Is it time to do away with it? - Test install on all tested Python versions -- cgit v1.2.1