1 TODO/bugs in Irssi SILC client
2 ==============================
4 o /cmode #c +p says "not channel operator" even though is operator.
6 o /WHOIS without arguments should so client's own info.
8 o Do not let the Irssi show the passphrase of the channel on the screen.
10 o Do not execute PING for invalid entities.
12 o Do not let irssi u pdate the status bar on JOIN until the join command
13 is successful, so that it does not update that I'm on the channel
14 even though I could not join the channel.
16 o The CMODE notify handling in client library may return NULL
17 client entry pointer to the application (when server was the CMODE's
18 executor). Fix this somehow.
20 o Add PERL scripting support from Irssi CVS.
22 o Add local commands to list the current server and client public keys
23 that the user has. And a local command to dump the contents of the
24 public key to the screen. Something like LISTKEYS, SHOWKEY...
26 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
27 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
30 o Extend the /HELP command to support sub commands or something. So
31 that user can say /help set mutual_authentication they would get
32 help of the mutual_authentication setting.
34 o Set different kind of settings, like, /set mutual_authentication,
35 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
38 TODO/bugs In SILC Client Library
39 ================================
41 o Library should save the cumode and not start from 0 everytime then
44 o Add some silc_client_del_client and other deletion funtions for
45 application to delete client entrys from the cache.
47 o All protocol execution timeouts are hard coded. They should be
48 configurable and the Irssi SILC client should be able to set them
49 with for example /set key_exchange_timeout etc. The silc_client_alloc
50 should take a Params structure or something as argument.
52 o silc_client_close_connection leaks memory. Read the XXX from code.
54 o Some of the ops->say's should be removed and moved to the application
55 from the library. Go through these.
57 o The client library must manage somehow when receiving client that has
58 same nickname, same server, same username but different Client ID than
59 what we have in the cache. It is now assumed that they are different
60 client but it might not be. It should at least number the clients
61 using the client->num so that they can be accessed from the user
62 interface separately or it could just remove the old client unless
63 it is on some channels.
65 o Add client library parameters or options that handle what kind of
66 messages the library should print out (using `say' client operation,
67 for example) and what is left for the application to print. The
68 appliation could for example set that it handles all command printing
69 but all error printing should be handled by the library, etc...
70 This is not a showstopper.
73 TODO/bugs In SILC Server
74 ========================
76 o When server quits and all clients of that server are removed from all
77 channels the channel keys are re-generated for all clients. This is
78 a bug and should be done only once per channel after all clients of
79 the server has been removed.
81 o Incomplete IPv6 support:
83 o silc_server_get_users_on_channel does not support IPv6 based
85 o silc_server_route_get and the route code in general supports
87 o silcd/serverid.c and its routines supports only IPv4.
89 o DNS/IP lookup blocks the server. This must be fixed. Check the
90 resolver stuff (resolver(3), resolver(5)). Either we have to do the
91 own resolver stuff (through scheduler, if possible without writing
92 too much own stuff) or use threads.
94 o The backup router support described in the protocol specification
95 should be done at some point.
97 o New configuration file format must be added. The new one will be
98 done using the dotconf config library (lib/dotconf). The following
99 tasks relates closely to this as well and must be done at the same time
100 when adding the new config file format:
102 o Server says that it is able to listen on multiple ports but
103 currently that is bogus. It can, but internals are for single
106 o Protocol execution timeouts are hard coded, should be
109 o IP address fields in configuration file should accept mask
110 format as well, IP/MASK, and not just plain IP.
112 o Connection classes should be actually implemented in
113 serverconfig.c. They can be defined but they are totally
114 ignored currently. And they should be redefined also.
117 TODO/bugs In SILC Libraries
118 ===========================
120 o Incomplete IPv6 support:
122 o All network routines in lib/silcutil/silcnet.[ch] does not
124 o silc_id_render supports only IPv4 based ID's in the file
125 lib/silcutil/silcutil.c.
127 o Compression routines are missing. The protocol supports packet
128 compression thus it must be implemented. SILC Comp API must be
129 defined. zlib package is already included into the lib dir (in CVS,
130 not in distribution), but it is not used yet, and it requires some
131 tweaking on the Makefiles (we want static lib not shared).
133 o The CAST cipher is not compiled currently due to compilation errors;
134 check those. Cast is in lib/silccrypt/cast.c.
136 o All payload parsing (decoding) functions should take unsigned char *
137 and uint32 as data and data length as arguments. Now some of the
138 routines do already that but most of the routines use SilcBuffer.
139 The SilcBuffer ones should be removed since buf->data and buf->len
140 is more convenient to use. However, the silc_buffer_[un]format
141 routines support only SilcBuffer so they would require reallocation
142 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
143 should be added silc_buffer_[un]format_? routines. These are currently
144 only cosmetic changes but at some point must be done to make the
145 payload interfaces consistent.
147 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
148 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
152 TODO In SILC Protocol
153 =====================
157 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
158 messages is signed with the senders private key and thus can
159 be verified with its public key. This is especially handy
160 feature when sending privat messages without having negotiated
161 private keys, thus the servers decrypts and re-ecnrypts the
162 messages. Other applications exists as well.
164 o If channel founder mode is set and the invite mode is set on channel
165 then the founder should be added to the list automatically so that
166 if the founder signoff's it will be able join again to the invite only
167 channel wihtout being invited.
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.