1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Giving KILL command crashes the client.
6 o Waiting the answer for accepting new key after the protocol has
7 timeout and then ansering Y will crash the client.
9 o Add PERL scripting support from Irssi CVS.
11 o Add local commands to list the current server and client public keys
12 that the user has. And a local command to dump the contents of the
13 public key to the screen. Something like LISTKEYS, SHOWKEY...
15 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
16 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
19 o Extend the /HELP command to support sub commands or something. So
20 that user can say /help set mutual_authentication they would get
21 help of the mutual_authentication setting.
23 o Set different kind of settings, like, /set mutual_authentication,
24 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
26 o Add KNOCKOUT local command. It should kick an client from channel and
27 set a ban for it for number of seconds.
29 o Add KICKBAN local command. Kicks and bans the specified client.
31 o Do some /set show_mail_notification that would show a notification
32 on screen when new email is received.
35 TODO/bugs In SILC Client Library
36 ================================
38 o If the silc_client_channel_message does not find the client entry
39 then it should attempt to resolve it at least once and no return
40 NULL entry to the application.
42 o All protocol execution timeouts are hard coded. They should be
43 configurable and the Irssi SILC client should be able to set them
44 with for example /set key_exchange_timeout etc. The silc_client_alloc
45 should take a Params structure or something as argument.
47 o silc_client_close_connection leaks memory. Read the XXX from code.
49 o Some of the ops->say's should be removed and moved to the application
50 from the library. Go through these.
52 o The client library must manage somehow when receiving client that has
53 same nickname, same server, same username but different Client ID than
54 what we have in the cache. It is now assumed that they are different
55 client but it might not be. It should at least number the clients
56 using the client->num so that they can be accessed from the user
57 interface separately or it could just remove the old client unless
58 it is on some channels.
60 o Add client library parameters or options that handle what kind of
61 messages the library should print out (using `say' client operation,
62 for example) and what is left for the application to print. The
63 appliation could for example set that it handles all command printing
64 but all error printing should be handled by the library, etc...
65 This is not a showstopper.
68 TODO/bugs In SILC Server
69 ========================
71 o Seems that router does not announce its client to the connecting
72 server when server announces its clients on the channel.
74 o When server quits and all clients of that server are removed from all
75 channels the channel keys are re-generated for all clients. This is
76 a bug and should be done only once per channel after all clients of
77 the server has been removed.
79 o Incomplete IPv6 support:
81 o silc_server_get_users_on_channel does not support IPv6 based
83 o silc_server_route_get and the route code in general supports
85 o silcd/serverid.c and its routines supports only IPv4.
87 o DNS/IP lookup blocks the server. This must be fixed. Check the
88 resolver stuff (resolver(3), resolver(5)). Either we have to do the
89 own resolver stuff (through scheduler, if possible without writing
90 too much own stuff) or use threads.
92 o The backup router support described in the protocol specification
93 should be done at some point.
95 o New configuration file format must be added. The new one will be
96 done using the dotconf config library (lib/dotconf). The following
97 tasks relates closely to this as well and must be done at the same time
98 when adding the new config file format:
100 o Server says that it is able to listen on multiple ports but
101 currently that is bogus. It can, but internals are for single
104 o Protocol execution timeouts are hard coded, should be
107 o IP address fields in configuration file should accept mask
108 format as well, IP/MASK, and not just plain IP.
110 o Connection classes should be actually implemented in
111 serverconfig.c. They can be defined but they are totally
112 ignored currently. And they should be redefined also.
115 TODO/bugs In SILC Libraries
116 ===========================
118 o The timeout calculation can go negative at least on BSD, so rewrite
119 in in lib/silcutil/silcschdule.c.
121 o Incomplete IPv6 support:
123 o All network routines in lib/silcutil/silcnet.[ch] does not
125 o silc_id_render supports only IPv4 based ID's in the file
126 lib/silcutil/silcutil.c.
128 o Compression routines are missing. The protocol supports packet
129 compression thus it must be implemented. SILC Comp API must be
130 defined. zlib package is already included into the lib dir (in CVS,
131 not in distribution), but it is not used yet, and it requires some
132 tweaking on the Makefiles (we want static lib not shared).
134 o The CAST cipher is not compiled currently due to compilation errors;
135 check those. Cast is in lib/silccrypt/cast.c.
137 o All payload parsing (decoding) functions should take unsigned char *
138 and uint32 as data and data length as arguments. Now some of the
139 routines do already that but most of the routines use SilcBuffer.
140 The SilcBuffer ones should be removed since buf->data and buf->len
141 is more convenient to use. However, the silc_buffer_[un]format
142 routines support only SilcBuffer so they would require reallocation
143 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
144 should be added silc_buffer_[un]format_? routines. These are currently
145 only cosmetic changes but at some point must be done to make the
146 payload interfaces consistent.
148 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
149 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
153 TODO In SILC Protocol
154 =====================
158 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
159 messages is signed with the senders private key and thus can
160 be verified with its public key. This is especially handy
161 feature when sending privat messages without having negotiated
162 private keys, thus the servers decrypts and re-ecnrypts the
163 messages. Other applications exists as well.
169 o Pthreads support. A lot of problems are solved with server (and with
170 client as well) if we add pthread support. We can forget things such
171 as non-blocking connecting etc, and we can do things such as DNS/IP
172 lookups async. The server itself also benefits great deal from
173 threads, especially from performance point of view.
175 But, this is not a small task and almost entire SILC Library has to
176 be made re-entrant. Own API is probably added for the threads support
177 to make changes in the future as painless as possible. So the API
178 would have things like silc_mutex_lock, silc_mutex_unlock and
181 o X.509 certificate support. SILC protocol supports certificates and
182 it would be great to have support for them. This is a big task as
183 support has to be made for ASN.1 as well. I've looked into OpenSSL
184 package as it has X.509 certificate support (and ASN.1 as well).
185 The code does not look very good to my eye but it has some potentials.
186 This should be looked at more closely.
188 Naturally own SILC Certificate API has to be defined regardles what
189 the actual X.509 library is (OpenSSL X.509 or something else). Other
190 choice is to write own X.509 library but I'm not going to do it -
191 I can help to migrate the OpenSSL X.509 into SILC and I can help if
192 someone would like to write the X.509 library - but I'm not going
193 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
196 o SSH2 public keys support. Maybe - not really needed but could be
197 nice as SSH is widely used all over the place. SILC Protocol
198 supports SSH2 public keys.
200 o Cipher optimizations (asm, that this) at least for i386 would be nice.