summaryrefslogtreecommitdiff
path: root/python-3-changes.txt
diff options
context:
space:
mode:
authorThorsten Behrens <sbehrens@gmx.li>2011-01-02 03:24:57 -0500
committerThorsten Behrens <sbehrens@gmx.li>2011-01-02 03:24:57 -0500
commit560874f4b8711897ea644b8f5817113e7221dbec (patch)
tree8ee688c1ec7b7b74956ed40d5b2d9dcf7b6ad38d /python-3-changes.txt
parent5dc2f8f216a49ff2254dc1edc451904e188e5e9b (diff)
downloadpycrypto-560874f4b8711897ea644b8f5817113e7221dbec.tar.gz
Update documentation with current state of security of hash and cipher
functions. Update documentation with Python 3.x notes.
Diffstat (limited to 'python-3-changes.txt')
-rw-r--r--python-3-changes.txt11
1 files changed, 1 insertions, 10 deletions
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