1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Do not let irssi update the status bar on JOIN until the join command
5 is successful, so that it does not update that I'm on the channel
6 even though I could not join the channel.
8 o The CMODE notify handling in client library may return NULL
9 client entry pointer to the application (when server was the CMODE's
10 executor). Fix this somehow.
12 o Add PERL scripting support from Irssi CVS.
14 o Add local commands to list the current server and client public keys
15 that the user has. And a local command to dump the contents of the
16 public key to the screen. Something like LISTKEYS, SHOWKEY...
18 o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
19 cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
22 o Extend the /HELP command to support sub commands or something. So
23 that user can say /help set mutual_authentication they would get
24 help of the mutual_authentication setting.
26 o Set different kind of settings, like, /set mutual_authentication,
27 /set key_exchange_timeout, /set conn_auth_timeout etc etc.
30 TODO/bugs In SILC Client Library
31 ================================
33 o Library should save the cumode and not start from 0 everytime then
34 CUMODE is issued. A mechanism of getting the channel entry for
35 CMODE and CUMODE by the command reply identifier must be added.
36 Otherwise saving the modes for the channels and channel user
37 entries are impossible since server does not send Channel ID as
38 command reply in these commands.
40 o All protocol execution timeouts are hard coded. They should be
41 configurable and the Irssi SILC client should be able to set them
42 with for example /set key_exchange_timeout etc. The silc_client_alloc
43 should take a Params structure or something as argument.
45 o silc_client_close_connection leaks memory. Read the XXX from code.
47 o The client library must manage somehow when receiving client that has
48 same nickname, same server, same username but different Client ID than
49 what we have in the cache. It is now assumed that they are different
50 client but it might not be. It should at least number the clients
51 using the client->num so that they can be accessed from the user
52 interface separately or it could just remove the old client unless
53 it is on some channels.
56 TODO/bugs In SILC Server
57 ========================
59 o Incomplete IPv6 support:
61 o silc_server_get_users_on_channel does not support IPv6 based
63 o silc_server_route_get and the route code in general supports
65 o silcd/serverid.c and its routines supports only IPv4.
67 o DNS/IP lookup blocks the server. This must be fixed. Check the
68 resolver stuff (resolver(3), resolver(5)). Either we have to do the
69 own resolver stuff (through scheduler, if possible without writing
70 too much own stuff) or use threads.
72 o The backup router support described in the protocol specification
73 should be done at some point.
75 o New configuration file format must be added. The new one will be
76 done using the dotconf config library (lib/dotconf). The following
77 tasks relates closely to this as well and must be done at the same time
78 when adding the new config file format:
80 o Server says that it is able to listen on multiple ports but
81 currently that is bogus. It can, but internals are for single
84 o Protocol execution timeouts are hard coded, should be
87 o IP address fields in configuration file should accept mask
88 format as well, IP/MASK, and not just plain IP.
90 o Connection classes should be actually implemented in
91 serverconfig.c. They can be defined but they are totally
92 ignored currently. And they should be redefined also.
95 TODO/bugs In SILC Libraries
96 ===========================
98 o Incomplete IPv6 support:
100 o All network routines in lib/silcutil/silcnet.[ch] does not
102 o silc_id_render supports only IPv4 based ID's in the file
103 lib/silcutil/silcutil.c.
105 o Compression routines are missing. The protocol supports packet
106 compression thus it must be implemented. SILC Comp API must be
107 defined. zlib package is already included into the lib dir (in CVS,
108 not in distribution), but it is not used yet, and it requires some
109 tweaking on the Makefiles (we want static lib not shared).
111 o All payload parsing (decoding) functions should take unsigned char *
112 and uint32 as data and data length as arguments. Now some of the
113 routines do already that but most of the routines use SilcBuffer.
114 The SilcBuffer ones should be removed since buf->data and buf->len
115 is more convenient to use. However, the silc_buffer_[un]format
116 routines support only SilcBuffer so they would require reallocation
117 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
118 should be added silc_buffer_[un]format_? routines. These are currently
119 only cosmetic changes but at some point must be done to make the
120 payload interfaces consistent.
122 o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
123 SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
127 TODO In SILC Protocol
128 =====================
132 o Add SILC_MESSAGE_FLAG_SIGNED flag that indicates that the
133 messages is signed with the senders private key and thus can
134 be verified with its public key. This is especially handy
135 feature when sending privat messages without having negotiated
136 private keys, thus the servers decrypts and re-ecnrypts the
137 messages. Other applications exists as well.
139 o If channel founder mode is set and the invite mode is set on channel
140 then the founder should be added to the list automatically so that
141 if the founder signoff's it will be able join again to the invite only
142 channel wihtout being invited.
148 o Pthreads support. A lot of problems are solved with server (and with
149 client as well) if we add pthread support. We can forget things such
150 as non-blocking connecting etc, and we can do things such as DNS/IP
151 lookups async. The server itself also benefits great deal from
152 threads, especially from performance point of view.
154 But, this is not a small task and almost entire SILC Library has to
155 be made re-entrant. Own API is probably added for the threads support
156 to make changes in the future as painless as possible. So the API
157 would have things like silc_mutex_lock, silc_mutex_unlock and
160 o X.509 certificate support. SILC protocol supports certificates and
161 it would be great to have support for them. This is a big task as
162 support has to be made for ASN.1 as well. I've looked into OpenSSL
163 package as it has X.509 certificate support (and ASN.1 as well).
164 The code does not look very good to my eye but it has some potentials.
165 This should be looked at more closely.
167 Naturally own SILC Certificate API has to be defined regardles what
168 the actual X.509 library is (OpenSSL X.509 or something else). Other
169 choice is to write own X.509 library but I'm not going to do it -
170 I can help to migrate the OpenSSL X.509 into SILC and I can help if
171 someone would like to write the X.509 library - but I'm not going
172 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
175 Other package that should be checked is the NSS's X509 library.
177 o SSH2 public keys support. Maybe - not really needed but could be
178 nice as SSH is widely used all over the place. SILC Protocol
179 supports SSH2 public keys.
181 o Cipher optimizations (asm, that this) at least for i386 would be nice.