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