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 When server quits and all clients of that server are removed from all
30 channels the channel keys are re-generated for all clients. This is
31 a bug and should be done only once per channel after all clients of
32 the server has been removed.
34 o Acceptance of incoming connections (client and server connections)
35 should be checked before key exchange protocol. Currently it is
36 checked at the authentication phase after KE, that is ok, but it should
37 be checked before starting KE, as well. This should be done so that
38 is first checks denied connections, then client connections and then
39 server connections. There is no use to execute the SKE if the connection
42 o DNS/IP lookup blocks the server. This must be fixed. Check the
43 resolver stuff (resolver(3), resolver(5)). Either we have to do the
44 own resolver stuff (through scheduler, if possible without writing
45 too much own stuff) or use threads.
47 o The backup router support described in the protocol specification
48 should be done at some point.
50 o Server says that it is able to listen on multiple ports but currently
51 that is bogus. It can, but internals are for single server.
53 o Protocol execution timeouts are hard coded, should be configurable.
55 o IP address fields in configuration file should accept mask format
56 as well, IP/MASK, and not just plain IP.
58 o Connection classes should be actually implemented in serverconfig.c.
59 They can be defined but they are totally ignored currently. And they
60 should be redefined also.
63 TODO/bugs In SILC Libraries
64 ===========================
66 o Compression routines are missing. The protocol supports packet
67 compression thus it must be implemented. SILC Comp API must be
68 defined. zlib package is already included into the lib dir (in CVS,
69 not in distribution), but it is not used yet, and it requires some
70 tweaking on the Makefiles (we want static lib not shared).
72 o Random Number Generator needs some tweaking. Reading /dev/random may
73 block resulting slow initialization of RNG. Some other things in the
74 RNG may block as well. Also, I have some pending changes to the RNG
75 that needs to be commited (from Schneier's Yarrow-160 paper). They
76 should make the RNG even better.
78 o SIM support for SILC PKCS API needs to made so that they could be
79 used as SIM's. At the same time some work is required on prime
80 generation as the way it is done now sucks. Read from code for
87 o Pthreads support. A lot of problems are solved with server (and with
88 client as well) if we add pthread support. We can forget things such
89 as non-blocking connecting etc, and we can do things such as DNS/IP
90 lookups async. The server itself also benefits great deal from
91 threads, especially from performance point of view.
93 But, this is not a small task and almost entire SILC Library has to
94 be made re-entrant. Own API is probably added for the threads support
95 to make changes in the future as painless as possible. So the API
96 would have things like silc_mutex_lock, silc_mutex_unlock and
99 o X.509 certificate support. SILC protocol supports certificates and
100 it would be great to have support for them. This is a big task as
101 support has to be made for ASN.1 as well. I've looked into OpenSSL
102 package as it has X.509 certificate support (and ASN.1 as well).
103 The code does not look very good to my eye but it has some potentials.
104 This should be looked at more closely.
106 Naturally own SILC Certificate API has to be defined regardles what
107 the actual X.509 library is (OpenSSL X.509 or something else). Other
108 choice is to write own X.509 library but I'm not going to do it -
109 I can help to migrate the OpenSSL X.509 into SILC and I can help if
110 someone would like to write the X.509 library - but I'm not going
111 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
114 o SSH2 public keys support. Maybe - not really needed but could be
115 nice as SSH is widely used all over the place. SILC Protocol
116 supports SSH2 public keys.
118 o Cipher optimizations (asm, that this) at least for i386 would be nice.