X-Git-Url: http://git.silcnet.org/gitweb/?a=blobdiff_plain;f=TODO-1.0;h=73e5a27bc4c2bbffb83c63e54fe1872255e611ff;hb=413da0f8686910f5e627393157566ae729ca99c4;hp=1f821fdec6d46fc5714ef2984521c080f15762c1;hpb=7431bd61b7149a1b25ccd969cfbb05316ff9fa59;p=silc.git

diff --git a/TODO-1.0 b/TODO-1.0
index 1f821fde..73e5a27b 100644
--- 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 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.
@@ -116,6 +124,14 @@ least could be done.
 	  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
@@ -164,20 +180,4 @@ least could be done.
 
  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).