1 TODO/bugs In SILC Client Library
2 ================================
4 o Client library crashes if for example server timeouts protocol
5 execution and disconnects the client. The client, on the other hand
6 may still assume that the connection is active, even after receiving
7 the EOF. Reason for this is that the clien library does not handle
8 the SilcSocketConnection reference counter at all. This must be
11 o When receiving client's public key with GETKEY or in key agreement
12 protoocl it probably should be saved using the nickname and the real
13 name of the client instead of the host name of the client.
15 o Add client library parameters or options that handle what kind of
16 messages the library should print out (using `say' client operation,
17 for example) and what is left for the application to print. The
18 appliation could for example set that it handles all command printing
19 but all error printing should be handled by the library, etc...
20 This is not a showstopper.
22 o Input line on UI is buggy. Cursor movement etc bugs. Too lazy to
26 TODO/bugs In SILC Server
27 ========================
29 o Send SILC_NOTIFY_TYPE_CUMODE_CHANGE when received announced channels
30 and channel users and we (router) already has a channel founder on the
33 o When server quits and all clients of that server are removed from all
34 channels the channel keys are re-generated for all clients. This is
35 a bug and should be done only once per channel after all clients of
36 the server has been removed.
38 o DNS/IP lookup blocks the server. This must be fixed. Check the
39 resolver stuff (resolver(3), resolver(5)). Either we have to do the
40 own resolver stuff (through scheduler, if possible without writing
41 too much own stuff) or use threads.
43 o [DenyConnection] config section is not implemented.
45 o The backup router support described in the protocol specification
46 should be done at some point.
48 o Server says that it is able to listen on multiple ports but currently
49 that is bogus. It can, but internals are for single server.
51 o Protocol execution timeouts are hard coded, should be configurable.
53 o IP address fields in configuration file should accept mask format
54 as well, IP/MASK, and not just plain IP.
56 o Connection classes should be actually implemented in serverconfig.c.
57 They can be defined but they are totally ignored currently. And they
58 should be redefined also.
61 TODO/bugs In SILC Libraries
62 ===========================
64 o Remove the static lists from SILC ciphers, PKCS and hash functions
65 in the crypto library. The currently acceptable code is used in the
66 HMAC library, look from there. The config file must decide the order
67 of the algorithms, not the static lists, as they are doing now.
68 Actually the way to do this is to keep the static lists, but register
69 the algorithms to the dynamic list and make the alloc routines to
70 check only the dynamic list. Also, replace the lists used by these
71 routines with SilcList. Also, for applications it might be nice
72 to export a function that registers default algorithms, if application
73 does not want to register them one by one (if for example SILC client
74 is run without config files at all).
76 o Compression routines are missing. The protocol supports packet
77 compression thus it must be implemented. SILC Comp API must be
78 defined. zlib package is already included into the lib dir (in CVS,
79 not in distribution), but it is not used yet, and it requires some
80 tweaking on the Makefiles (we want static lib not shared).
82 o Some of the ciphers in lib/silccrypt does not implement the SILC
85 o IPv6 support for ID's and into the code.
87 o SIM support for SILC PKCS API needs to made so that they could be
88 used as SIM's. At the same time some work is required on prime
89 generation as the way it is done now sucks. Read from code for
96 o Pthreads support. A lot of problems are solved with server (and with
97 client as well) if we add pthread support. We can forget things such
98 as non-blocking connecting etc, and we can do things such as DNS/IP
99 lookups async. The server itself also benefits great deal from
100 threads, especially from performance point of view.
102 But, this is not a small task and almost entire SILC Library has to
103 be made re-entrant. Own API is probably added for the threads support
104 to make changes in the future as painless as possible. So the API
105 would have things like silc_mutex_lock, silc_mutex_unlock and
108 o X.509 certificate support. SILC protocol supports certificates and
109 it would be great to have support for them. This is a big task as
110 support has to be made for ASN.1 as well. I've looked into OpenSSL
111 package as it has X.509 certificate support (and ASN.1 as well).
112 The code does not look very good to my eye but it has some potentials.
113 This should be looked at more closely.
115 Naturally own SILC Certificate API has to be defined regardles what
116 the actual X.509 library is (OpenSSL X.509 or something else). Other
117 choice is to write own X.509 library but I'm not going to do it -
118 I can help to migrate the OpenSSL X.509 into SILC and I can help if
119 someone would like to write the X.509 library - but I'm not going
120 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
123 o SSH2 public keys support. Maybe - not really needed but could be
124 nice as SSH is widely used all over the place. SILC Protocol
125 supports SSH2 public keys.
127 o Cipher optimizations (asm, that this) at least for i386 would be nice.