1 TODO/bugs in Irssi SILC client
2 ==============================
4 o GETKEY server will save the serverkey to the same filename as the
5 connected server and thus destroys the key.
7 o GETKEY server will show first, "there is no such nickname".
9 o Add local command to switch the channel's private key when channel has
10 several private keys. Currently sending channel messages with many
11 keys is not possible because changing the key is not possible by the
14 o JOINing to +a (requires passphrase to JOIN) does not work on autojoin.
15 Seems the passwords in the .silc/config has no effect.
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 Add PERL scripting support from Irssi CVS.
27 o Extend the /HELP command to support sub commands or something. So
28 that user can say /help set mutual_authentication they would get
29 help of the mutual_authentication setting.
31 o Set different kind of settings, like, /set mutual_authentication,
32 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
35 TODO/bugs In SILC Client Library
36 ================================
38 o The PRIVATE_MESSAGE_KEY packet is not handled (it is implemented
39 though). This should be added and perhaps new client operation
40 should be added to notify application that it was received and
41 set the key only if application wishes to set (accept the key) it.
43 o should /nick nick and /nick Nick cause the Nick to be Nick@host becase
46 o When changing own nickname and there exists a same nickname the library
47 can give the client now nickname in format nick@host. This is new
48 behaviour and maybe should be removed. The changer should always
49 get the one it wants and not have the formatted nickname.
51 o Remove the command destructor all together from the client, it is
52 not needed and its usage is buggy when the context is registered
53 to multiple pending commands.
55 o Additions to do after protocol version 1.1:
57 o Fix the NICK_CHANGE notify handling not to create new entry
58 for the changed client, but take the nickname from the notify
59 (removes need for resolving as well). Protocol TODO entry 3.
61 o Add support for list of errors in command replies. Protocol
65 TODO/bugs In SILC Server
66 ========================
68 o Backup router related issues
70 o Channel user mode changes are notified unnecessarely when
71 switching to backup router on router crash.
73 o Add a timeout to handling incoming JOIN commands. It should be
74 enforced that JOIN command is executed only once in a second or two
75 seconds. Now it is possible to accept n incoming JOIN commands
76 and process them without any timeouts. THis must be employed because
77 each JOIN command will create and distribute the new channel key
78 to everybody on the channel.
80 o New configuration file format must be added. The new one will be
81 done using the dotconf config library (lib/dotconf). The following
82 tasks relates closely to this as well and must be done at the same time
83 when adding the new config file format:
85 o Server says that it is able to listen on multiple ports but
86 currently that is bogus. It can, but internals are for single
89 o Protocol execution timeouts are hard coded, should be
92 o IP address fields in configuration file should accept mask
93 format as well, IP/MASK, and not just plain IP.
95 o If client's public key is saved in the server (and doing public key
96 authentication) then the hostname and the username information could
97 be taken from the public key. Should be a configuration option!
100 TODO/bugs In SILC Libraries
101 ===========================
103 o WIN32 silc_net_create_connection_async does not work the same way
104 than on Unix. Do it with threads on WIN32. The function works but
105 is not actually async currently.
107 o Rewrite the lib/silcsim/silcsim.h. The SilcSimContext should be
108 private and silc_sim_alloc should take necessary arguments.
111 TODO in SILC Protocol
112 =====================
114 Current protocol version is 1.0. However, it is far from being perfect,
115 and needs to include additional features. Following protocol TODO entries
116 describe new stuff to be added to protocol versions 1.x.
118 1. Re-define the Status Payload: it is now 16 bits, split it into two
119 8 bits fields. First field includes status types from 0 - 9 and
120 10 - n *if* it is not an list of errors. If it is list of errors then
121 the first field includes 1, 2 and/or 3, and the second field includes
122 the error status 10 - n. This way it is possible to send multiple
123 errors (list of errors) and we have a way to tell the receiver that
124 there will be other errors as well. The second field is used only
125 if there is list of errors. If normal status, or normal (single)
126 error status the second field is set to zero, and must be ignored.
127 Hence, the status works same way as now except for list of errors.
128 To be included in protocol version 1.1.
130 2. Define that WHOIS and IDENTIFY commands must send list of errors
131 if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
132 requested and was not found. Each unfound entry must cause an error
133 command reply to the sender. Also define that errors must be sent
134 *after* sending successfully found entries (this way receiver may
135 ignore them). To be included in protocol version 1.1.
137 3. Define the NICK_CHANGE notify to send the changed nickname as a new
138 third argument. This will make the NICK_CHANGE notify handling easier
139 in the receiver's end (client primarily) since it removes the
140 requirement that receiver must resolve (using IDENTIFY or WHOIS) the
141 new Client ID received in the notify (because of the new nickname is
142 unknown). To be included in protocol version 1.1.
144 4. Add "request parameters" or similar to the WHOIS command, which can
145 be used to request various parameters (something not returned by
146 standard WHOIS command) about clients (info that could be fetched
147 even from clients). Additional specification (or appendix) should
148 be done to define the payload and the parameters. It could be used
149 to make the WHOIS command support various search conditions as well.
150 This would be the way to extend the WHOIS command to support various
151 new features without always making the command incompatible to previous
152 version. To be included in protocol version 1.1.
154 5. Inviting and banning by public key should be made possible. To be
155 included in protocol version 1.x.
157 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
158 can be used to silence (moderate) normal users and opers (this set
159 only by founder). To be included in protocol version 1.1.
161 7. Channel Message Payload needs slight redesining to include the IV
162 field to the MAC generation of the payload. It is authenticated
163 by the packet's MAC but not by the payload's MAC. Since the IV
164 belongs to the payload, its integrity should be protected by the
165 payload MAC and not alone by packet MAC. To be included in protocol
172 A rough list of stuff that is going to be done to SILC after 1.0 or at
175 o Implement the defined SilcDH API. The definition is in
176 lib/silccrypt/silcdh.h.
178 o X.509 certificate support. SILC protocol supports certificates and
179 it would be great to have support for them. This is a big task as
180 support has to be made for ASN.1 as well. I've looked into OpenSSL
181 package as it has X.509 certificate support (and ASN.1 as well).
182 The code does not look very good to my eye but it has some potentials.
183 This should be looked at more closely.
185 Naturally own SILC Certificate API has to be defined regardles what
186 the actual X.509 library is (OpenSSL X.509 or something else). Other
187 choice is to write own X.509 library but I'm not going to do it -
188 I can help to migrate the OpenSSL X.509 into SILC and I can help if
189 someone would like to write the X.509 library - but I'm not going
190 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
193 Other package that should be checked is the NSS's X509 library,
194 which I like more over OpenSSL package.
196 o SSH2 public keys support, allowing the use of SSH2 public keys in
199 o OpenPGP certificate support, allowing the use of PGP public keys
202 o Compression routines are missing. The protocol supports packet
203 compression thus it must be implemented. SILC Zip API must be
206 o Rewrite the lib/silcutil/silcprotocol.[ch] not to have [un]register
207 functions, but to make it context based all the way. The alloc should
208 take as argument the protocol type and its callback (not only
209 final callback). It is not good that we have now global list of
210 registered protocols.
212 o Optimizations in Libraries
214 o There is currently three (3) allocations per packet in the
215 silc_packet_receive_process, which is used to process and
216 dispatch all packets in the packet queue to the parser callback
217 function. First allocation is for parse_ctx, second for the
218 SilcPacketContext, and third for packet->buffer where the actual
221 The parse_ctx allocation can be removed by adding it as a
222 structure to the SilcPacketContext. When the SilcPacketContext
223 is allocated there is space for the parse context already.
225 The silc_packet_context_alloc could have a free list of
226 packet contexts. If free packet context is found from the list
227 it is returned instead of allocating a new one. The library
228 could at first allocate them and save them to the free list
229 until enough contexts for smooth processing exists in the list.
230 This would remove a big allocation since the structure is
231 quite big, and even bigger if it would include the parse_ctx.
233 The packet->buffer can be optimized too if the SilcBuffer
234 interface would support free lists as well. Maybe such could
235 be done in the same way as for SilcPacketContext. The
236 silc_buffer_alloc would check free list before actually
237 allocating new memory. Since the packets in the SILC protocol
238 usually are about the same size (due to padding) it would be
239 easy to find suitable size buffer from the free list very
242 These naturally cause the overal memory consumption to grow
243 but would take away many allocations that can be done several
246 o Move the actual file descriptor task callback (the callback that
247 handles the incoming data, outgoing data etc, that is implemnted
248 in server and client separately (silc_server_packet_process and
249 silc_client_packet_proces)) to the low level socket connection
250 handling routines, and create an interface where the application
251 can register a callbacks for incoming data, outoing data and EOF
252 receiving, which the library will call when necessary. This way
253 we can move the data handling in one place.
255 o Add silc_id_str2id to accept the destination buffer as argument
256 and thus not require any memory allocation. Same will happen
257 with silc_id_payload_* functions.
259 o Optimizations in Server
261 o Remove the big switch statement from the function
262 silc_server_packet_parse_type and replace it with predefined
263 table of function pointers where each of the slot in table
264 represents the packet type value.
266 Same could be done with notify packets which has big switch
267 statement too. Same kind of table of notify callbacks could be
270 o The parser callback in the server will add a timeout task for
271 all packets. It will require registering and allocating a
272 new task to the SilcSchedule. Maybe, at least, for server
273 and router packets the parser would be called immediately
274 instead of adding it to the scheduler with 0 timeout. It
275 should be analyzed too how slow the task registering process
276 actually is, and find out ways to optimize it.
278 o Cipher optimizations (asm, that this) at least for i386 would be nice.
280 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
281 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled