1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Add PERL scripting support from Irssi CVS.
6 o Add local commands to list the current server and client public keys
7 that the user has. And a local command to dump the contents of the
8 public key to the screen. Something like LISTKEYS, SHOWKEY...
10 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
11 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
14 o Extend the /HELP command to support sub commands or something. So
15 that user can say /help set mutual_authentication they would get
16 help of the mutual_authentication setting.
18 o Set different kind of settings, like, /set mutual_authentication,
19 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
22 TODO/bugs In SILC Client Library
23 ================================
25 o Add some silc_client_del_client and other deletion funtions for
26 application to delete client entrys from the cache.
28 o All protocol execution timeouts are hard coded. They should be
29 configurable and the Irssi SILC client should be able to set them
30 with for example /set key_exchange_timeout etc. The silc_client_alloc
31 should take a Params structure or something as argument.
33 o silc_client_close_connection leaks memory. Read the XXX from code.
35 o Some of the ops->say's should be removed and moved to the application
36 from the library. Go through these.
38 o The client library must manage somehow when receiving client that has
39 same nickname, same server, same username but different Client ID than
40 what we have in the cache. It is now assumed that they are different
41 client but it might not be. It should at least number the clients
42 using the client->num so that they can be accessed from the user
43 interface separately or it could just remove the old client unless
44 it is on some channels.
46 o Add client library parameters or options that handle what kind of
47 messages the library should print out (using `say' client operation,
48 for example) and what is left for the application to print. The
49 appliation could for example set that it handles all command printing
50 but all error printing should be handled by the library, etc...
51 This is not a showstopper.
54 TODO/bugs In SILC Server
55 ========================
57 o When server quits and all clients of that server are removed from all
58 channels the channel keys are re-generated for all clients. This is
59 a bug and should be done only once per channel after all clients of
60 the server has been removed.
62 o Incomplete IPv6 support:
64 o silc_server_get_users_on_channel does not support IPv6 based
66 o silc_server_route_get and the route code in general supports
68 o silcd/serverid.c and its routines supports only IPv4.
70 o DNS/IP lookup blocks the server. This must be fixed. Check the
71 resolver stuff (resolver(3), resolver(5)). Either we have to do the
72 own resolver stuff (through scheduler, if possible without writing
73 too much own stuff) or use threads.
75 o The backup router support described in the protocol specification
76 should be done at some point.
78 o New configuration file format must be added. The new one will be
79 done using the dotconf config library (lib/dotconf). The following
80 tasks relates closely to this as well and must be done at the same time
81 when adding the new config file format:
83 o Server says that it is able to listen on multiple ports but
84 currently that is bogus. It can, but internals are for single
87 o Protocol execution timeouts are hard coded, should be
90 o IP address fields in configuration file should accept mask
91 format as well, IP/MASK, and not just plain IP.
93 o Connection classes should be actually implemented in
94 serverconfig.c. They can be defined but they are totally
95 ignored currently. And they should be redefined also.
98 TODO/bugs In SILC Libraries
99 ===========================
101 o Incomplete IPv6 support:
103 o All network routines in lib/silcutil/silcnet.[ch] does not
105 o silc_id_render supports only IPv4 based ID's in the file
106 lib/silcutil/silcutil.c.
108 o Compression routines are missing. The protocol supports packet
109 compression thus it must be implemented. SILC Comp API must be
110 defined. zlib package is already included into the lib dir (in CVS,
111 not in distribution), but it is not used yet, and it requires some
112 tweaking on the Makefiles (we want static lib not shared).
114 o The CAST cipher is not compiled currently due to compilation errors;
115 check those. Cast is in lib/silccrypt/cast.c.
117 o All payload parsing (decoding) functions should take unsigned char *
118 and uint32 as data and data length as arguments. Now some of the
119 routines do already that but most of the routines use SilcBuffer.
120 The SilcBuffer ones should be removed since buf->data and buf->len
121 is more convenient to use. However, the silc_buffer_[un]format
122 routines support only SilcBuffer so they would require reallocation
123 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
124 should be added silc_buffer_[un]format_? routines. These are currently
125 only cosmetic changes but at some point must be done to make the
126 payload interfaces consistent.
128 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
129 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
133 TODO In SILC Protocol
134 =====================
138 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
139 messages is signed with the senders private key and thus can
140 be verified with its public key. This is especially handy
141 feature when sending privat messages without having negotiated
142 private keys, thus the servers decrypts and re-ecnrypts the
143 messages. Other applications exists as well.
149 o Pthreads support. A lot of problems are solved with server (and with
150 client as well) if we add pthread support. We can forget things such
151 as non-blocking connecting etc, and we can do things such as DNS/IP
152 lookups async. The server itself also benefits great deal from
153 threads, especially from performance point of view.
155 But, this is not a small task and almost entire SILC Library has to
156 be made re-entrant. Own API is probably added for the threads support
157 to make changes in the future as painless as possible. So the API
158 would have things like silc_mutex_lock, silc_mutex_unlock and
161 o X.509 certificate support. SILC protocol supports certificates and
162 it would be great to have support for them. This is a big task as
163 support has to be made for ASN.1 as well. I've looked into OpenSSL
164 package as it has X.509 certificate support (and ASN.1 as well).
165 The code does not look very good to my eye but it has some potentials.
166 This should be looked at more closely.
168 Naturally own SILC Certificate API has to be defined regardles what
169 the actual X.509 library is (OpenSSL X.509 or something else). Other
170 choice is to write own X.509 library but I'm not going to do it -
171 I can help to migrate the OpenSSL X.509 into SILC and I can help if
172 someone would like to write the X.509 library - but I'm not going
173 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
176 o SSH2 public keys support. Maybe - not really needed but could be
177 nice as SSH is widely used all over the place. SILC Protocol
178 supports SSH2 public keys.
180 o Cipher optimizations (asm, that this) at least for i386 would be nice.