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 ID List must be optimized. When the lists grow the searching
41 becomes a lot slower and is some cases the lists are searched many
42 times, like with channel messages (twice at least). Some sort of
43 hash tables should replace the lists. Thus, the ID cache should be
44 rewritten to use hash tables internally.
46 o New configuration file format must be added. The new one will be
47 done using the dotconf config library.
49 o The backup router support described in the protocol specification
50 should be done at some point.
52 o Server says that it is able to listen on multiple ports but currently
53 that is bogus. It can, but internals are for single server.
55 o Protocol execution timeouts are hard coded, should be configurable.
57 o IP address fields in configuration file should accept mask format
58 as well, IP/MASK, and not just plain IP.
60 o Connection classes should be actually implemented in serverconfig.c.
61 They can be defined but they are totally ignored currently. And they
62 should be redefined also.
65 TODO/bugs In SILC Libraries
66 ===========================
68 o Incomplete IPv6 support:
70 o All network routines in lib/silcutil/silcnet.[ch] does not
73 o Hash tables must be implemented.
75 o Compression routines are missing. The protocol supports packet
76 compression thus it must be implemented. SILC Comp API must be
77 defined. zlib package is already included into the lib dir (in CVS,
78 not in distribution), but it is not used yet, and it requires some
79 tweaking on the Makefiles (we want static lib not shared).
81 o The CAST cipher is not compiled currently due to compilation errors;
82 check those. Cast is in lib/silccrypt/cast.c.
88 o Pthreads support. A lot of problems are solved with server (and with
89 client as well) if we add pthread support. We can forget things such
90 as non-blocking connecting etc, and we can do things such as DNS/IP
91 lookups async. The server itself also benefits great deal from
92 threads, especially from performance point of view.
94 But, this is not a small task and almost entire SILC Library has to
95 be made re-entrant. Own API is probably added for the threads support
96 to make changes in the future as painless as possible. So the API
97 would have things like silc_mutex_lock, silc_mutex_unlock and
100 o X.509 certificate support. SILC protocol supports certificates and
101 it would be great to have support for them. This is a big task as
102 support has to be made for ASN.1 as well. I've looked into OpenSSL
103 package as it has X.509 certificate support (and ASN.1 as well).
104 The code does not look very good to my eye but it has some potentials.
105 This should be looked at more closely.
107 Naturally own SILC Certificate API has to be defined regardles what
108 the actual X.509 library is (OpenSSL X.509 or something else). Other
109 choice is to write own X.509 library but I'm not going to do it -
110 I can help to migrate the OpenSSL X.509 into SILC and I can help if
111 someone would like to write the X.509 library - but I'm not going
112 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
115 o SSH2 public keys support. Maybe - not really needed but could be
116 nice as SSH is widely used all over the place. SILC Protocol
117 supports SSH2 public keys.
119 o Cipher optimizations (asm, that this) at least for i386 would be nice.