1 TODO/bugs In SILC Client Library
2 ================================
4 o Add local commands to list the current server and client public keys
5 that the user has. And a local command to dump the contents of the
6 public key to the screen.
8 o Add client library parameters or options that handle what kind of
9 messages the library should print out (using `say' client operation,
10 for example) and what is left for the application to print. The
11 appliation could for example set that it handles all command printing
12 but all error printing should be handled by the library, etc...
13 This is not a showstopper.
15 o Input line on UI is buggy. Cursor movement etc bugs. Too lazy to
19 TODO/bugs In SILC Server
20 ========================
22 o When server quits and all clients of that server are removed from all
23 channels the channel keys are re-generated for all clients. This is
24 a bug and should be done only once per channel after all clients of
25 the server has been removed.
27 o Incomplete IPv6 support:
29 o silc_server_get_users_on_channel does not support IPv6 based
31 o silc_server_route_get and the route code in general supports
33 o silcd/serverid.c and its routines supports only IPv4.
35 o DNS/IP lookup blocks the server. This must be fixed. Check the
36 resolver stuff (resolver(3), resolver(5)). Either we have to do the
37 own resolver stuff (through scheduler, if possible without writing
38 too much own stuff) or use threads.
40 o The backup router support described in the protocol specification
41 should be done at some point.
43 o New configuration file format must be added. The new one will be
44 done using the dotconf config library (lib/dotconf). The following
45 tasks relates closely to this as well and must be done at the same time
46 when adding the new config file format:
48 o Server says that it is able to listen on multiple ports but
49 currently that is bogus. It can, but internals are for single
52 o Protocol execution timeouts are hard coded, should be
55 o IP address fields in configuration file should accept mask
56 format as well, IP/MASK, and not just plain IP.
58 o Connection classes should be actually implemented in
59 serverconfig.c. They can be defined but they are totally
60 ignored currently. And they should be redefined also.
63 TODO/bugs In SILC Libraries
64 ===========================
66 o Incomplete IPv6 support:
68 o All network routines in lib/silcutil/silcnet.[ch] does not
70 o silc_id_render supports only IPv4 based ID's in the file
71 lib/silcutil/silcutil.c.
73 o Compression routines are missing. The protocol supports packet
74 compression thus it must be implemented. SILC Comp API must be
75 defined. zlib package is already included into the lib dir (in CVS,
76 not in distribution), but it is not used yet, and it requires some
77 tweaking on the Makefiles (we want static lib not shared).
79 o The CAST cipher is not compiled currently due to compilation errors;
80 check those. Cast is in lib/silccrypt/cast.c.
82 o All payload parsing (decoding) functions should take unsigned char *
83 and uint32 as data and data length as arguments. Now some of the
84 routines do already that but most of the routines use SilcBuffer.
85 The SilcBuffer ones should be removed since buf->data and buf->len
86 is more convenient to use. However, the silc_buffer_[un]format
87 routines support only SilcBuffer so they would require reallocation
88 of SilcBuffer. Maybe support for raw data (and not just SilcBuffer)
89 should be added silc_buffer_[un]format_? routines. These are currently
90 only cosmetic changes but at some point must be done to make the
91 payload interfaces consistent.
97 o Pthreads support. A lot of problems are solved with server (and with
98 client as well) if we add pthread support. We can forget things such
99 as non-blocking connecting etc, and we can do things such as DNS/IP
100 lookups async. The server itself also benefits great deal from
101 threads, especially from performance point of view.
103 But, this is not a small task and almost entire SILC Library has to
104 be made re-entrant. Own API is probably added for the threads support
105 to make changes in the future as painless as possible. So the API
106 would have things like silc_mutex_lock, silc_mutex_unlock and
109 o X.509 certificate support. SILC protocol supports certificates and
110 it would be great to have support for them. This is a big task as
111 support has to be made for ASN.1 as well. I've looked into OpenSSL
112 package as it has X.509 certificate support (and ASN.1 as well).
113 The code does not look very good to my eye but it has some potentials.
114 This should be looked at more closely.
116 Naturally own SILC Certificate API has to be defined regardles what
117 the actual X.509 library is (OpenSSL X.509 or something else). Other
118 choice is to write own X.509 library but I'm not going to do it -
119 I can help to migrate the OpenSSL X.509 into SILC and I can help if
120 someone would like to write the X.509 library - but I'm not going
121 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
124 o SSH2 public keys support. Maybe - not really needed but could be
125 nice as SSH is widely used all over the place. SILC Protocol
126 supports SSH2 public keys.
128 o Cipher optimizations (asm, that this) at least for i386 would be nice.