Merged silc_1_0_branch to trunk.

[silc.git] / TODO

diff --git a/TODO b/TODO
index fb406ebf08244fe59856794c6d19d51355ec9b14..e1c30b328f58a8ef9a9a301eb2113f60a1b252a8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,22 +1,28 @@
-TODO for Irssi SILC Client 1.0
-==============================
+TODO for SILC Client 1.0 branch
+===============================
 
- 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 Bugs reported on the mailing list that will be fixed eventually.
+   The numbers are arbitrary and assigned by me (c0ffee), bugs in
+   parentheses are fixed.
+
+   (#1    Ignore ALL doesn't ignore target using /me)
+   #2    specification of the silc network
+   (#3    expired private key dialogue doesn't work)
+   #4    silc client allows setting non-utf8 topics
+   #5    SILC-client displaying wrong totals with /names
 
 
 TODO for SILC Server 1.0
 ========================
 
- o INVITE and BAN notifys send the entire list as notify, but only the
-   added/removed info should be sent.
-
- o The CMODE cipher & hmac change problem (#101).
+ o BUG: silc_idlist_del_client had been called but sock->user_data remained
+   and pointed to invalid pointer.  Where it was called is not known.
 
- o Fix CUMODE_CHANGE and CMODE_CHANGE for founder key things.
+ o Basic UTF-8 stringprep profile that makes sure UTF-8 strings are
+   as defined in spec-08 section 3.13.
 
- o 1.2 backup router support
+ o Server sometimes connects more than once to router and keeps
+   connecting even though connection exists.
 
  o Testing
 
@@ -24,17 +30,18 @@ TODO for SILC Server 1.0
 TODO/bugs In SILC Libraries
 ===========================
 
- 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/
 
+ o Implement new version of SFTP protocol (missing versions 4 and 5, we
+   have version 3).
+
 
 TODO in Toolkit Documentation
 =============================
 
-Stuff that needs to be done in order to complete the Tooolkit Reference
+Stuff that needs to be done in order to complete the Toolkit Reference
 Manual (Do these to 0.9.x).
 
  o Write "Programming with Toolkit" document, describing how to build
@@ -43,5 +50,5 @@ Manual (Do these to 0.9.x).
    example), and how external projects can use Toolkit without gluing into
    it (how to link etc), debugging, architecture, types, etc.
 
- o Searching of predefined keywords, exact and partial matches (would be 
+ o Searching of predefined keywords, exact and partial matches (would be
    nice).