X-Git-Url: http://git.silcnet.org/gitweb/?p=silc.git;a=blobdiff_plain;f=TODO;h=1d5f3a69a4ed8b2250c102941de176f167e1489e;hp=25f39441d4899195b8aee07e0236262e96d7ba0f;hb=382d15d447b7a95390decfa783836ae4fe255b3d;hpb=c08107c80b816558a1c48ada27eaf23840793157 diff --git a/TODO b/TODO index 25f39441..1d5f3a69 100644 --- a/TODO +++ b/TODO @@ -1,92 +1,39 @@ -TODO/bugs in Irssi SILC client +TODO for Irssi SILC Client 1.0 ============================== - o /cumode for unknown nick does not give any error message (Fix this to - 1.0). + 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 -TODO/bugs In SILC Client Library -================================ - - 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 1.0). - - o Remove conn->current_channel. - - o Additions to do after protocol version 1.1: - - o Add support for list of errors in command replies. Protocol - TODO entry 1. - - -TODO/bugs In SILC Server +TODO for SILC Server 1.0 ======================== - o Configuration file additions (Do this to 0.8.x): - - o Add incoming connection frequency, incoming connection frequency - for single IP address, key exchange frequency, key exchange - frequency for single IP. Add also frequency base. - - o If server send CUMODE_CHANGE notify (like setting founder) to router - and router does not have founder on channel (founder is left or there's - no founder on channel at all), the router will accept the server's - founder mode change, even though it perhaps should not do that (Fix - this to 0.9). - - o The router should check for validity of received notify packets from - routers (fix this to 0.9). Following NOTIFYs needs to be verified: - - o JOIN (check that joining is allowed) - o SIGNOFF (maybe should check that notifier owns the client) - - o Backup router related issues (Fix this to 1.0): + o Fix CUMODE_CHANGE and CMODE_CHANGE for founder key things. - o Channel user mode changes are notified unnecessarely when - switching to backup router on router crash. + o 1.2 backup router support - 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 1.0). - - 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 =========================== - 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 1.0). + 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 ============================= Stuff that needs to be done in order to complete the Tooolkit Reference -Manual (Do these to 0.9 and 1.0). - - o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h. +Manual (Do these to 0.9.x). - 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 @@ -98,50 +45,5 @@ Manual (Do these to 0.9 and 1.0). Toolkit support, what has been implemented, what has not been, what works differently etc. - -TODO in SILC Protocol -===================== - -Current protocol version is 1.0. However, it is far from being perfect, -and needs to include additional features. Following protocol TODO entries -describe new stuff to be added to protocol versions 1.x. - - 2. Define that WHOIS and IDENTIFY commands must send list of errors - if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was - requested and was not found. Each unfound entry must cause an error - command reply to the sender. Also define that errors must be sent - *after* sending successfully found entries (this way receiver may - ignore them). To be included in protocol version 1.1. - - 4. Add "request parameters" or similar to the WHOIS command, which can - be used to request various parameters (something not returned by - standard WHOIS command) about clients (info that could be fetched - even from clients). Additional specification (or appendix) should - be done to define the payload and the parameters. It could be used - to make the WHOIS command support various search conditions as well. - This would be the way to extend the WHOIS command to support various - new features without always making the command incompatible to previous - version. To be included in protocol version 1.1. - - 17. Cell wide channel founder support, and permanent channels when - founder mode set. - - 20. Services support? - - 21. Subscription/IRC's notify kind support? - - 22. Session detachment/resume? - - 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 Searching of predefined keywords, exact and partial matches (would be + nice).