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 All protocol execution timeouts are hard coded. They should be
39 configurable and the Irssi SILC client should be able to set them
40 with for example /set key_exchange_timeout etc. The silc_client_alloc
41 should take a Params structure or something as argument.
43 o silc_client_close_connection leaks memory. Read the XXX from code.
45 o Some of the ops->say's should be removed and moved to the application
46 from the library. Go through these.
48 o The client library must manage somehow when receiving client that has
49 same nickname, same server, same username but different Client ID than
50 what we have in the cache. It is now assumed that they are different
51 client but it might not be. It should at least number the clients
52 using the client->num so that they can be accessed from the user
53 interface separately or it could just remove the old client unless
54 it is on some channels.
56 o Add client library parameters or options that handle what kind of
57 messages the library should print out (using `say' client operation,
58 for example) and what is left for the application to print. The
59 appliation could for example set that it handles all command printing
60 but all error printing should be handled by the library, etc...
61 This is not a showstopper.
64 TODO/bugs In SILC Server
65 ========================
67 o When server quits and all clients of that server are removed from all
68 channels the channel keys are re-generated for all clients. This is
69 a bug and should be done only once per channel after all clients of
70 the server has been removed.
72 o Incomplete IPv6 support:
74 o silc_server_get_users_on_channel does not support IPv6 based
76 o silc_server_route_get and the route code in general supports
78 o silcd/serverid.c and its routines supports only IPv4.
80 o DNS/IP lookup blocks the server. This must be fixed. Check the
81 resolver stuff (resolver(3), resolver(5)). Either we have to do the
82 own resolver stuff (through scheduler, if possible without writing
83 too much own stuff) or use threads.
85 o The backup router support described in the protocol specification
86 should be done at some point.
88 o New configuration file format must be added. The new one will be
89 done using the dotconf config library (lib/dotconf). The following
90 tasks relates closely to this as well and must be done at the same time
91 when adding the new config file format:
93 o Server says that it is able to listen on multiple ports but
94 currently that is bogus. It can, but internals are for single
97 o Protocol execution timeouts are hard coded, should be
100 o IP address fields in configuration file should accept mask
101 format as well, IP/MASK, and not just plain IP.
103 o Connection classes should be actually implemented in
104 serverconfig.c. They can be defined but they are totally
105 ignored currently. And they should be redefined also.
108 TODO/bugs In SILC Libraries
109 ===========================
111 o The timeout calculation can go negative at least on BSD, so rewrite
112 in in lib/silcutil/silcschdule.c.
114 o Incomplete IPv6 support:
116 o All network routines in lib/silcutil/silcnet.[ch] does not
118 o silc_id_render supports only IPv4 based ID's in the file
119 lib/silcutil/silcutil.c.
121 o Compression routines are missing. The protocol supports packet
122 compression thus it must be implemented. SILC Comp API must be
123 defined. zlib package is already included into the lib dir (in CVS,
124 not in distribution), but it is not used yet, and it requires some
125 tweaking on the Makefiles (we want static lib not shared).
127 o The CAST cipher is not compiled currently due to compilation errors;
128 check those. Cast is in lib/silccrypt/cast.c.
130 o All payload parsing (decoding) functions should take unsigned char *
131 and uint32 as data and data length as arguments. Now some of the
132 routines do already that but most of the routines use SilcBuffer.
133 The SilcBuffer ones should be removed since buf->data and buf->len
134 is more convenient to use. However, the silc_buffer_[un]format
135 routines support only SilcBuffer so they would require reallocation
136 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
137 should be added silc_buffer_[un]format_? routines. These are currently
138 only cosmetic changes but at some point must be done to make the
139 payload interfaces consistent.
141 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
142 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
146 TODO In SILC Protocol
147 =====================
151 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
152 messages is signed with the senders private key and thus can
153 be verified with its public key. This is especially handy
154 feature when sending privat messages without having negotiated
155 private keys, thus the servers decrypts and re-ecnrypts the
156 messages. Other applications exists as well.
162 o Pthreads support. A lot of problems are solved with server (and with
163 client as well) if we add pthread support. We can forget things such
164 as non-blocking connecting etc, and we can do things such as DNS/IP
165 lookups async. The server itself also benefits great deal from
166 threads, especially from performance point of view.
168 But, this is not a small task and almost entire SILC Library has to
169 be made re-entrant. Own API is probably added for the threads support
170 to make changes in the future as painless as possible. So the API
171 would have things like silc_mutex_lock, silc_mutex_unlock and
174 o X.509 certificate support. SILC protocol supports certificates and
175 it would be great to have support for them. This is a big task as
176 support has to be made for ASN.1 as well. I've looked into OpenSSL
177 package as it has X.509 certificate support (and ASN.1 as well).
178 The code does not look very good to my eye but it has some potentials.
179 This should be looked at more closely.
181 Naturally own SILC Certificate API has to be defined regardles what
182 the actual X.509 library is (OpenSSL X.509 or something else). Other
183 choice is to write own X.509 library but I'm not going to do it -
184 I can help to migrate the OpenSSL X.509 into SILC and I can help if
185 someone would like to write the X.509 library - but I'm not going
186 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
189 o SSH2 public keys support. Maybe - not really needed but could be
190 nice as SSH is widely used all over the place. SILC Protocol
191 supports SSH2 public keys.
193 o Cipher optimizations (asm, that this) at least for i386 would be nice.