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