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