Merged from silc_1_0_branch.

[silc.git] / TODO

diff --git a/TODO b/TODO
index 3ab775e25ee3e5ff350abac419c471fa83b954ca..1d5f3a69a4ed8b2250c102941de176f167e1489e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,48 +1,29 @@
-TODO/bugs in Irssi SILC client
+TODO for Irssi SILC Client 1.0

 ==============================
 
 ==============================
 

-TODO/bugs In SILC Client Library
-================================
+ o Testing - See test plan:
+     http://silcnet.org/docs/silc-client-1.0-test.pdf
+     http://silcnet.org/docs/silc-client-1.0-test.ps

 
 

- o The PRIVATE_MESSAGE_KEY packet is not handled (it is implemented 
-   though).  This should be added and perhaps new client operation
-   should be added to notify application that it was received and
-   set the key only if application wishes to set (accept the key) it
-   (Do this to 0.9.x).

 
 

-
-TODO/bugs In SILC Server
+TODO for SILC Server 1.0

 ========================
 
 ========================
 

- o Implement the <Requested Attributes> and the Attribute Payload to
-   the core library, client and server.  Maybe implementations of
-   RFC 2425 and RFC 2426 to make it complete.
-
- o Backup router related issues (Fix this to 0.9.x):
-
-       o Channel user mode changes are notified unnecessarely when
-         switching to backup router on router crash.
+ o Fix CUMODE_CHANGE and CMODE_CHANGE for founder key things.

 
 

- o Add a timeout to handling incoming JOIN commands.  It should be 
-   enforced that JOIN command is executed only once in a second or two
-   seconds.  Now it is possible to accept n incoming JOIN commands
-   and process them without any timeouts.  THis must be employed because
-   each JOIN command will create and distribute the new channel key
-   to everybody on the channel (Fix this to 0.9.x).
+ o 1.2 backup router support

 
 

- o Lots of statistics updating is missing around the server.
-
- o If client's public key is saved in the server (and doing public key
-   authentication) then the hostname and the username information could
-   be taken from the public key.  Should be a configuration option!
+ o Testing

 
 
 TODO/bugs In SILC Libraries
 ===========================
 
 
 
 TODO/bugs In SILC Libraries
 ===========================
 

- o WIN32 silc_net_create_connection_async does not work the same way
-   than on Unix.  Do it with threads on WIN32.  The function works but
-   is not actually async currently (Fix this to 0.9.x).
+ o Test cases for all cryptographic primitive in lib/silccrypt/
+
+ o Test cases for all payload encoding and decoding routins in lib/silccore/
+
+ o Test cases for math library routines in lib/silcmath/

 
 
 TODO in Toolkit Documentation
 
 
 TODO in Toolkit Documentation


@@ -51,17 +32,8 @@ TODO in Toolkit Documentation
 Stuff that needs to be done in order to complete the Tooolkit Reference
 Manual (Do these to 0.9.x).
 
 Stuff that needs to be done in order to complete the Tooolkit Reference
 Manual (Do these to 0.9.x).
 

- o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h.
-
- o ROBOdoc documenting missing from lib/silcutil/silcdlist.h.
-
- o ROBOdoc documenting missing from lib/silcutil/silcfileutil.h.
-
- o ROBOdoc documenting missing from lib/silccrypt/silchash.h.
-
- o ROBOdoc documenting missing from lib/silccrypt/silccipher.h.
-
- o ROBOdoc documenting missing from lib/silccrypt/silcpkcs.h.
+ o Document the "notify" and "command_reply" client operations variable 
+   argument lists for all possible notify types and command replys.

 
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how
 
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how


@@ -72,3 +44,6 @@ Manual (Do these to 0.9.x).
  o Write "Platform Implementations" document to describe what platforms
    Toolkit support, what has been implemented, what has not been, what
    works differently etc.
  o Write "Platform Implementations" document to describe what platforms
    Toolkit support, what has been implemented, what has not been, what
    works differently etc.

+
+ o Searching of predefined keywords, exact and partial matches (would be 
+   nice).