[project @ akuchling-20020524212803-61f355dbc5fbed39]

[project @ 2002-05-24 14:28:03 by akuchling]
Updated file

2 files changed, 17 insertions, 18 deletions

diff --git a/ChangeLog b/ChangeLog
index 7c609e7..feb279a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,8 +9,12 @@
 	
 	* (Backwards incompatible) Restored the Crypto.Protocol package,
 	  and modernized and tidied up the two modules in it,
-	  AllOrNothing.py and Chaffing.py.
+	  AllOrNothing.py and Chaffing.py, renaming various methods
+	  and changing the interface.
 	  
+	* (Backwards incompatible) Changed the function names in
+	  Crypto.Util.RFC1751.
+	
 	* Restored the Crypto.PublicKey package at user request.  I
 	  think I'll leave it in the package and warn about it in the
 	  documentation.  I hope that eventually I can point to
@@ -24,10 +28,14 @@
 
 	* Fix endianness bugs that caused test case failures on Sparc,
 	  PPC, and doubtless other platforms.
-	  
+
 	* Added a test suite (requires Sancho, from 
 	  http://www.mems-exchange.org/software/sancho/)
 
+        * Added lots of docstrings, so 'pydoc Crypto' now produces 
+	  helpful output.  (Open question: maybe *all* of the documentation
+	  should be moved into docstrings?)
+	  
 	* Make test.py automatically add the build/* directory to sys.path.
 
 	* Removed 'inline' declaration from C functions.  Some compilers
diff --git a/TODO b/TODO
index 88f4303..a81ae34 100644
--- a/TODO
+++ b/TODO
@@ -1,29 +1,20 @@
 
-For 1.9alpha2:
+For 1.9alpha3:
+
+* Add more tests for random pool code?
 
-* Add test for random pool code, which seems the most buggy 
-  module in the package.
-  
 * Update documentation
 
+* Clean up markup in pycrypt.tex
+
+* Reformat all the code to MEMS Exchange style
+
 * Document the functions and macros for adding a new algorithm
     Hash functions:
   hash_init(), hash_copy(), DIGEST_SIZE, hash_update(), hash_digest()
     Block functions: 
   ...
 
-* Break backward compatibility.  The interfaces were invented around
-1995, back when I was younger and dumber.  I'd like to clean them up,
-cruelly breaking backward compatibility where necessary, and release
-the new code as version 2.0 to signal the magnitude of the changes.
-While we have the chance, we can also drop useless code, rename
-packages and classes, or whatever.
- 
-* Modernize the code to current standards (Distutils installation,
-docstrings, naming conventions, test suites).  
- 
-* Possibly add SHA256, SHA512.
-
 * Provide drop-in support for extensions/drivers like
 amkCrypto/mxCrypto. There should be some way to register these
 drivers in your package, e.g. by defining a certain subdirectory