1 TODO/bugs in Irssi SILC client
2 ==============================
4 o /NICK without arguments crashes the client
6 o /CMODE * +a without arguments crashes the client. Check other options
7 with arguments as well.
9 o /INVITE * nick crashes the remote client.
11 o Add PERL scripting support from Irssi CVS.
13 o Add KNOCKOUT local command. It should kick an client from channel and
14 set a ban for it for number of seconds.
16 o Add KICKBAN local command. Kicks and bans the specified client.
18 o Add local commands to list the current server and client public keys
19 that the user has. And a local command to dump the contents of the
20 public key to the screen. Something like LISTKEYS, SHOWKEY...
22 o Set different kind of settings, like, /set mutual_authentication,
23 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
25 o Extend the /HELP command to support sub commands or something. So
26 that user can say /help set mutual_authentication they would get
27 help of the mutual_authentication setting.
29 o Do some /set show_mail_notification that would show a notification
30 on screen when new email is received.
32 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
33 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
37 TODO/bugs In SILC Client Library
38 ================================
40 o All protocol execution timeouts are hard coded. They should be
41 configurable and the Irssi SILC client should be able to set them
42 with for example /set key_exchange_timeout etc. The silc_client_alloc
43 should take a Params structure or something as argument.
45 o silc_client_close_connection leaks memory. Read the XXX from code.
47 o Some of the ops->say's should be removed and moved to the application
48 from the library. Go through these.
50 o The client library must manage somehow when receiving client that has
51 same nickname, same server, same username but different Client ID than
52 what we have in the cache. It is now assumed that they are different
53 client but it might not be. It should at least number the clients
54 using the client->num so that they can be accessed from the user
55 interface separately or it could just remove the old client unless
56 it is on some channels.
58 o Add client library parameters or options that handle what kind of
59 messages the library should print out (using `say' client operation,
60 for example) and what is left for the application to print. The
61 appliation could for example set that it handles all command printing
62 but all error printing should be handled by the library, etc...
63 This is not a showstopper.
66 TODO/bugs In SILC Server
67 ========================
69 o When server quits and all clients of that server are removed from all
70 channels the channel keys are re-generated for all clients. This is
71 a bug and should be done only once per channel after all clients of
72 the server has been removed.
74 o Incomplete IPv6 support:
76 o silc_server_get_users_on_channel does not support IPv6 based
78 o silc_server_route_get and the route code in general supports
80 o silcd/serverid.c and its routines supports only IPv4.
82 o DNS/IP lookup blocks the server. This must be fixed. Check the
83 resolver stuff (resolver(3), resolver(5)). Either we have to do the
84 own resolver stuff (through scheduler, if possible without writing
85 too much own stuff) or use threads.
87 o The backup router support described in the protocol specification
88 should be done at some point.
90 o New configuration file format must be added. The new one will be
91 done using the dotconf config library (lib/dotconf). The following
92 tasks relates closely to this as well and must be done at the same time
93 when adding the new config file format:
95 o Server says that it is able to listen on multiple ports but
96 currently that is bogus. It can, but internals are for single
99 o Protocol execution timeouts are hard coded, should be
102 o IP address fields in configuration file should accept mask
103 format as well, IP/MASK, and not just plain IP.
105 o Connection classes should be actually implemented in
106 serverconfig.c. They can be defined but they are totally
107 ignored currently. And they should be redefined also.
110 TODO/bugs In SILC Libraries
111 ===========================
113 o Incomplete IPv6 support:
115 o All network routines in lib/silcutil/silcnet.[ch] does not
117 o silc_id_render supports only IPv4 based ID's in the file
118 lib/silcutil/silcutil.c.
120 o Compression routines are missing. The protocol supports packet
121 compression thus it must be implemented. SILC Comp API must be
122 defined. zlib package is already included into the lib dir (in CVS,
123 not in distribution), but it is not used yet, and it requires some
124 tweaking on the Makefiles (we want static lib not shared).
126 o The CAST cipher is not compiled currently due to compilation errors;
127 check those. Cast is in lib/silccrypt/cast.c.
129 o All payload parsing (decoding) functions should take unsigned char *
130 and uint32 as data and data length as arguments. Now some of the
131 routines do already that but most of the routines use SilcBuffer.
132 The SilcBuffer ones should be removed since buf->data and buf->len
133 is more convenient to use. However, the silc_buffer_[un]format
134 routines support only SilcBuffer so they would require reallocation
135 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
136 should be added silc_buffer_[un]format_? routines. These are currently
137 only cosmetic changes but at some point must be done to make the
138 payload interfaces consistent.
144 o Pthreads support. A lot of problems are solved with server (and with
145 client as well) if we add pthread support. We can forget things such
146 as non-blocking connecting etc, and we can do things such as DNS/IP
147 lookups async. The server itself also benefits great deal from
148 threads, especially from performance point of view.
150 But, this is not a small task and almost entire SILC Library has to
151 be made re-entrant. Own API is probably added for the threads support
152 to make changes in the future as painless as possible. So the API
153 would have things like silc_mutex_lock, silc_mutex_unlock and
156 o X.509 certificate support. SILC protocol supports certificates and
157 it would be great to have support for them. This is a big task as
158 support has to be made for ASN.1 as well. I've looked into OpenSSL
159 package as it has X.509 certificate support (and ASN.1 as well).
160 The code does not look very good to my eye but it has some potentials.
161 This should be looked at more closely.
163 Naturally own SILC Certificate API has to be defined regardles what
164 the actual X.509 library is (OpenSSL X.509 or something else). Other
165 choice is to write own X.509 library but I'm not going to do it -
166 I can help to migrate the OpenSSL X.509 into SILC and I can help if
167 someone would like to write the X.509 library - but I'm not going
168 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
171 o SSH2 public keys support. Maybe - not really needed but could be
172 nice as SSH is widely used all over the place. SILC Protocol
173 supports SSH2 public keys.
175 o Cipher optimizations (asm, that this) at least for i386 would be nice.