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