Merged silc_1_0_branch to trunk.

[silc.git] / TODO-1.0

diff --git a/TODO-1.0 b/TODO-1.0
index 7e37bd927ba491c73b342d530e4d70234e58dff3..73e5a27bc4c2bbffb83c63e54fe1872255e611ff 100644 (file)
--- a/TODO-1.0
+++ b/TODO-1.0
@@ -31,6 +31,14 @@ least could be done.
  o OpenPGP certificate support, allowing the use of PGP public keys
    in SILC.
 
  o OpenPGP certificate support, allowing the use of PGP public keys
    in SILC.
 

+ o SILC PKCS (silcpkcs.h) reorganizing when other PK supports added.
+   Move the SILC Public Key routines away from the crypto library into
+   the core library (silccore).  silc_pkcs_public/private_key_* routines
+   to silc_public/private_key_* routines.  The silc_public_key_* routines
+   should also automatically handle SILC Public Keys, and other keys
+   and certificates as well.  Add fe. silcpk.h into silccore.  It should
+   also include the Public Key Payload encoding and decoding routines.
+

  o Compression routines are missing.  The protocol supports packet
    compression thus it must be implemented.  SILC Zip API must be
    defined.
  o Compression routines are missing.  The protocol supports packet
    compression thus it must be implemented.  SILC Zip API must be
    defined.


@@ -116,6 +124,14 @@ least could be done.
          SIGNOFF of notify at all (using SIGNOFF takes the idea about
          SERVER_SIGNOFF away entirely).
 
          SIGNOFF of notify at all (using SIGNOFF takes the idea about
          SERVER_SIGNOFF away entirely).
 

+        o Another SERVER_SIGNOFF opt/bugfix:  Currently the signoff is
+          sent to a client if it is on same channel as the client that
+          signoffed.  However, the entire SERVER_SIGNOFF list is sent to
+          the client, ie. it may receive clients that was not on the 
+          same channel.  This is actually against the specs.  It must be
+          done per channel.  It shouldn't receive the whole list just
+          because one client happened to be on same channel.
+

        o See also ~/silcserver
 
  o Add SilcAsyncOperation to utility library.  Any function that takes
        o See also ~/silcserver
 
  o Add SilcAsyncOperation to utility library.  Any function that takes


@@ -144,6 +160,13 @@ least could be done.
    SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
    in separately.
 
    SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
    in separately.
 

+ 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 EPOC specific additions/changes required:
 
        o lib/silcutil/epoc routines missing or not completed.
  o EPOC specific additions/changes required:
 
        o lib/silcutil/epoc routines missing or not completed.


@@ -157,20 +180,4 @@ least could be done.
 
  o Check whether we can fully comply with RFC 2779.
 
 
  o Check whether we can fully comply with RFC 2779.
 

-
-TODO in SILC Protocol
-=====================
-
- o Inviting and banning by public key should be made possible.  To be
-   included in protocol version 1.2.
-
- o UTF-8 support/requirement for nicknames & channel names.  UTF-8 support
-   in terminals and OS's are so hazy that this matter is left for
-   consideration in next version of the protocol (1.2).  For good UTF-8
-   reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
-   What should CLI application do if it receives nickname that it cannot
-   display without messing up the terminal?  If UTF-8 is mandatory in 
-   SILC then SILC clients cannot be allowed to start on terminals that do
-   not support UTF-8 (which renders 98% of users unable to use CLI SILC
-   app without hacking their environment).  See also site
-   http://gratrix.net/unicode/
+ o The CMODE cipher & hmac change problem (#101).