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