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 Add client library parameters or options that handle what kind of
12 messages the library should print out (using `say' client operation,
13 for example) and what is left for the application to print. The
14 appliation could for example set that it handles all command printing
15 but all error printing should be handled by the library, etc...
16 This is not a showstopper.
18 o Input line on UI is buggy. Cursor movement etc bugs. Too lazy to
22 TODO/bugs In SILC Server
23 ========================
25 o When server quits and all clients of that server are removed from all
26 channels the channel keys are re-generated for all clients. This is
27 a bug and should be done only once per channel after all clients of
28 the server has been removed.
30 o Acceptance of incoming connections (client and server connections)
31 should be checked before key exchange protocol. Currently it is
32 checked at the authentication phase after KE, that is ok, but it should
33 be checked before starting KE, as well. This should be done so that
34 is first checks denied connections, then client connections and then
35 server connections. There is no use to execute the SKE if the connection
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 Server says that it is able to listen on multiple ports but currently
44 that is bogus. It can, but internals are for single server.
46 o Protocol execution timeouts are hard coded, should be configurable.
48 o IP address fields in configuration file should accept mask format
49 as well, IP/MASK, and not just plain IP.
51 o Connection classes should be actually implemented in serverconfig.c.
52 They can be defined but they are totally ignored currently. And they
53 should be redefined also.
56 TODO/bugs In SILC Libraries
57 ===========================
59 o Implement PFS (Perfect Forward Secrecy) flag in SKE (and in client and
60 server, actually). If PFS is set, re-key must cause new key exchange.
61 This is required by the SILC protocol.
63 o Re-key in general is actually missing (from everywhere) and must be done.
65 o Compression routines are missing. The protocol supports packet
66 compression thus it must be implemented. SILC Comp API must be
67 defined. zlib package is already included into the lib dir (in CVS,
68 not in distribution), but it is not used yet, and it requires some
69 tweaking on the Makefiles (we want static lib not shared).
71 o Random Number Generator needs some tweaking. Reading /dev/random may
72 block resulting slow initialization of RNG. Some other things in the
73 RNG may block as well. Also, I have some pending changes to the RNG
74 that needs to be commited (from Schneier's Yarrow-160 paper). They
75 should make the RNG even better.
77 o SIM support for SILC PKCS API needs to made so that they could be
78 used as SIM's. At the same time some work is required on prime
79 generation as the way it is done now sucks. Read from code for
83 TODO in the protocol before SILC 0.x
84 ====================================
86 o New commands and features in the commands
87 (draft-riikonen-silc-spec-xx.txt):
89 o Define GETKEY command to fetch the public key of a server
90 and/or a client in the SILC Network.
91 o Define SENDKEY command to send your public key to a client
92 in the network. Sending to the server must not be done due
93 to various security reasons (the server must not trust the
94 public keys blindly without third party verification; that's
95 why SENDKEY is not for servers).
101 o Pthreads support. A lot of problems are solved with server (and with
102 client as well) if we add pthread support. We can forget things such
103 as non-blocking connecting etc, and we can do things such as DNS/IP
104 lookups async. The server itself also benefits great deal from
105 threads, especially from performance point of view.
107 But, this is not a small task and almost entire SILC Library has to
108 be made re-entrant. Own API is probably added for the threads support
109 to make changes in the future as painless as possible. So the API
110 would have things like silc_mutex_lock, silc_mutex_unlock and
113 o X.509 certificate support. SILC protocol supports certificates and
114 it would be great to have support for them. This is a big task as
115 support has to be made for ASN.1 as well. I've looked into OpenSSL
116 package as it has X.509 certificate support (and ASN.1 as well).
117 The code does not look very good to my eye but it has some potentials.
118 This should be looked at more closely.
120 Naturally own SILC Certificate API has to be defined regardles what
121 the actual X.509 library is (OpenSSL X.509 or something else). Other
122 choice is to write own X.509 library but I'm not going to do it -
123 I can help to migrate the OpenSSL X.509 into SILC and I can help if
124 someone would like to write the X.509 library - but I'm not going
125 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
128 o SSH2 public keys support. Maybe - not really needed but could be
129 nice as SSH is widely used all over the place. SILC Protocol
130 supports SSH2 public keys.
132 o Cipher optimizations (asm, that this) at least for i386 would be nice.