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 Add PERL scripting support from Irssi CVS.
10 o Add local commands to list the current server and client public keys
11 that the user has. And a local command to dump the contents of the
12 public key to the screen. Something like LISTKEYS, SHOWKEY...
14 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
15 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
18 o Extend the /HELP command to support sub commands or something. So
19 that user can say /help set mutual_authentication they would get
20 help of the mutual_authentication setting.
22 o Set different kind of settings, like, /set mutual_authentication,
23 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
25 o Add KNOCKOUT local command. It should kick an client from channel and
26 set a ban for it for number of seconds.
28 o Add KICKBAN local command. Kicks and bans the specified client.
30 o Do some /set show_mail_notification that would show a notification
31 on screen when new email is received.
34 TODO/bugs In SILC Client Library
35 ================================
37 o Add some silc_client_del_client and other deletion funtions for
38 application to delete client entrys from the cache.
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 Seems that router does not announce its client to the connecting
70 server when server announces its clients on the channel.
72 o When server quits and all clients of that server are removed from all
73 channels the channel keys are re-generated for all clients. This is
74 a bug and should be done only once per channel after all clients of
75 the server has been removed.
77 o Incomplete IPv6 support:
79 o silc_server_get_users_on_channel does not support IPv6 based
81 o silc_server_route_get and the route code in general supports
83 o silcd/serverid.c and its routines supports only IPv4.
85 o DNS/IP lookup blocks the server. This must be fixed. Check the
86 resolver stuff (resolver(3), resolver(5)). Either we have to do the
87 own resolver stuff (through scheduler, if possible without writing
88 too much own stuff) or use threads.
90 o The backup router support described in the protocol specification
91 should be done at some point.
93 o New configuration file format must be added. The new one will be
94 done using the dotconf config library (lib/dotconf). The following
95 tasks relates closely to this as well and must be done at the same time
96 when adding the new config file format:
98 o Server says that it is able to listen on multiple ports but
99 currently that is bogus. It can, but internals are for single
102 o Protocol execution timeouts are hard coded, should be
105 o IP address fields in configuration file should accept mask
106 format as well, IP/MASK, and not just plain IP.
108 o Connection classes should be actually implemented in
109 serverconfig.c. They can be defined but they are totally
110 ignored currently. And they should be redefined also.
113 TODO/bugs In SILC Libraries
114 ===========================
116 o Incomplete IPv6 support:
118 o All network routines in lib/silcutil/silcnet.[ch] does not
120 o silc_id_render supports only IPv4 based ID's in the file
121 lib/silcutil/silcutil.c.
123 o Compression routines are missing. The protocol supports packet
124 compression thus it must be implemented. SILC Comp API must be
125 defined. zlib package is already included into the lib dir (in CVS,
126 not in distribution), but it is not used yet, and it requires some
127 tweaking on the Makefiles (we want static lib not shared).
129 o The CAST cipher is not compiled currently due to compilation errors;
130 check those. Cast is in lib/silccrypt/cast.c.
132 o All payload parsing (decoding) functions should take unsigned char *
133 and uint32 as data and data length as arguments. Now some of the
134 routines do already that but most of the routines use SilcBuffer.
135 The SilcBuffer ones should be removed since buf->data and buf->len
136 is more convenient to use. However, the silc_buffer_[un]format
137 routines support only SilcBuffer so they would require reallocation
138 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
139 should be added silc_buffer_[un]format_? routines. These are currently
140 only cosmetic changes but at some point must be done to make the
141 payload interfaces consistent.
143 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
144 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
148 TODO In SILC Protocol
149 =====================
153 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
154 messages is signed with the senders private key and thus can
155 be verified with its public key. This is especially handy
156 feature when sending privat messages without having negotiated
157 private keys, thus the servers decrypts and re-ecnrypts the
158 messages. Other applications exists as well.
164 o Pthreads support. A lot of problems are solved with server (and with
165 client as well) if we add pthread support. We can forget things such
166 as non-blocking connecting etc, and we can do things such as DNS/IP
167 lookups async. The server itself also benefits great deal from
168 threads, especially from performance point of view.
170 But, this is not a small task and almost entire SILC Library has to
171 be made re-entrant. Own API is probably added for the threads support
172 to make changes in the future as painless as possible. So the API
173 would have things like silc_mutex_lock, silc_mutex_unlock and
176 o X.509 certificate support. SILC protocol supports certificates and
177 it would be great to have support for them. This is a big task as
178 support has to be made for ASN.1 as well. I've looked into OpenSSL
179 package as it has X.509 certificate support (and ASN.1 as well).
180 The code does not look very good to my eye but it has some potentials.
181 This should be looked at more closely.
183 Naturally own SILC Certificate API has to be defined regardles what
184 the actual X.509 library is (OpenSSL X.509 or something else). Other
185 choice is to write own X.509 library but I'm not going to do it -
186 I can help to migrate the OpenSSL X.509 into SILC and I can help if
187 someone would like to write the X.509 library - but I'm not going
188 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
191 o SSH2 public keys support. Maybe - not really needed but could be
192 nice as SSH is widely used all over the place. SILC Protocol
193 supports SSH2 public keys.
195 o Cipher optimizations (asm, that this) at least for i386 would be nice.