-TODO/bugs in Irssi SILC client
+TODO for Irssi SILC Client 1.0
==============================
- o Add local command to switch the channel's private key when channel has
- several private keys. Currently sending channel messages with many
- keys is not possible because changing the key is not possible by the
- user.
+ 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 JOINing to +a (requires passphrase to JOIN) does not work on autojoin.
- Seems the passwords in the .silc/config has no effect.
- o Add local commands to list the current server and client public keys
- that the user has. And a local command to dump the contents of the
- public key to the screen. Something like LISTKEYS, SHOWKEY...
-
- o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
- cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
- file.
-
- o Add PERL scripting support from Irssi CVS.
-
- o Extend the /HELP command to support sub commands or something. So
- that user can say /help set mutual_authentication they would get
- help of the mutual_authentication setting.
-
- o Set different kind of settings, like, /set mutual_authentication,
- /set key_exchange_timeout, /set conn_auth_timeout etc etc.
-
-
-TODO/bugs In SILC Client Library
-================================
-
- o Process the NO_SUCH_CLIENT_ID for WHOIS and IDENTIFY, since it can
- be received for example after sending MSG to non-existent client.
- It actually should be done always when it is received and the old
- entry should be removed.
-
- Doing this now however causes that /msg nick might give "no such nick"
- for the first time, and then after the entry is removed /msg nick
- may actually to go any nick client, which is not desired behaviour.
- The /msg must be fixed to use the specific nickname user typed
- (nick must not match nick@host).
-
-
-TODO/bugs In SILC Server
+TODO for SILC Server 1.0
========================
- o Backup router related issues
+ 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.
-
- o New configuration file format must be added. The new one will be
- done using the dotconf config library (lib/dotconf). The following
- tasks relates closely to this as well and must be done at the same time
- when adding the new config file format:
-
- o Server says that it is able to listen on multiple ports but
- currently that is bogus. It can, but internals are for single
- server.
-
- o Protocol execution timeouts are hard coded, should be
- configurable.
-
- o IP address fields in configuration file should accept mask
- format as well, IP/MASK, and not just plain IP.
-
- o Connection classes should be actually implemented in
- serverconfig.c. They can be defined but they are totally
- ignored currently. And they should be redefined also.
-
- 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.
-
- o Do not let the silcdefs.h lay around in distributions.
-
-
-TODO After 1.0
-==============
+ o Test cases for all cryptographic primitive in lib/silccrypt/
- o Compression routines are missing. The protocol supports packet
- compression thus it must be implemented. SILC Zip API must be
- defined. zlib package is already included into the lib dir (in CVS,
- not in distribution), but it is not used yet, and it requires some
- tweaking on the Makefiles (we want static lib not shared).
+ o Test cases for all payload encoding and decoding routins in lib/silccore/
- o Implement the defined SilcDH API. The definition is in
- lib/silccrypt/silcdh.h.
+ o Test cases for math library routines in lib/silcmath/
- o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
- SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
- in separately.
- o X.509 certificate support. SILC protocol supports certificates and
- it would be great to have support for them. This is a big task as
- support has to be made for ASN.1 as well. I've looked into OpenSSL
- package as it has X.509 certificate support (and ASN.1 as well).
- The code does not look very good to my eye but it has some potentials.
- This should be looked at more closely.
+TODO in Toolkit Documentation
+=============================
- Naturally own SILC Certificate API has to be defined regardles what
- the actual X.509 library is (OpenSSL X.509 or something else). Other
- choice is to write own X.509 library but I'm not going to do it -
- I can help to migrate the OpenSSL X.509 into SILC and I can help if
- someone would like to write the X.509 library - but I'm not going
- to start writing one myself. Anyhow, the OpenSSL X.509 lib should
- be checked.
+Stuff that needs to be done in order to complete the Tooolkit Reference
+Manual (Do these to 0.9.x).
- Other package that should be checked is the NSS's X509 library,
- which I like more over OpenSSL package.
+ o Document the "notify" and "command_reply" client operations variable
+ argument lists for all possible notify types and command replys.
- o SSH2 public keys support.
+ o Write "Programming with Toolkit" document, describing how to build
+ Toolkit, how the build system works, where is everything, how
+ new (external) projects can be glued into Toolkit (use irssi as an
+ example), and how external projects can use Toolkit without gluing into
+ it (how to link etc), debugging, architecture, types, etc.
- o OpenPGP certificate support.
+ o Write "Platform Implementations" document to describe what platforms
+ Toolkit support, what has been implemented, what has not been, what
+ works differently etc.
- o Cipher optimizations (asm, that this) at least for i386 would be nice.
+ o Searching of predefined keywords, exact and partial matches (would be
+ nice).