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