4 This is more or less complete list of tasks that has to be done before
5 SILC 1.0 could ever be released. It is clear that the list does not
6 include all the bugs that exists. At the end of list are tasks that
7 needs to be done but are probably post 1.0.
9 Feel free to contribute if you have the ability and free time - all the
10 help is really appreciated - and needed.
18 o We should replace all short, int, long, unsigned short, unsigned int,
19 unsigned long with some pre-defined datatypes that really are what
20 we want on all platforms. int16, uint16, int32, uint32 etc. are
21 what we could use or maybe SilcInt16, SilcUInt16 etc. Also, boolean
22 datatype should be defined.
25 TODO In SILC Client Library
26 ===========================
28 o TODO in commands (silc/local_command.c, lib/silcclient/command.c and
29 silc/silclient/command_reply.c):
31 o Local command to handle private message keys is not done
32 o Local command to handle channel private keys is not done
33 o Local command to handle key agreement protocol is not done
34 o RESTART command is not implemented
36 o Client library crashes if for example server timeouts protocol
37 execution and disconnects the client. The client, on the other hand
38 may still assume that the connection is active, even after receiving
39 the EOF. Reason for this is that the clien library does not handle
40 the SilcSocketConnection reference counter at all. This must be
43 o Logic for handling multiple same nicknames for example in private
44 message sending. I guess the logic is done in server side but is
47 o I guess, public key authentication (when connecting to a server)
48 is not working currently. It is just matter of loading the keys
49 from file and using them (see corresponding code in server, it should
50 support public key authentication already).
52 o Non-blocking connection on the background must be stopped if some
53 other connection on same window has established. Now it is possible
54 that some non-blocking connection timeouts on the background when
55 we already have a working connection to some other place; things
58 o Add client library parameters or options that handle what kind of
59 messages the library should print out (using `say' client operation,
60 for example) and what is left for the application to print. The
61 appliation could for example set that it handles all command printing
62 but all error printing should be handled by the library, etc...
63 This is not a showstopper.
65 o Input line on UI is buggy. Cursor movement etc bugs. Too lazy to
72 o TODO in commands (command.c and command_reply.c):
74 o RESTART is not implemented
75 o In servers all command reply funtions should still call the
76 pending command reply even if the reply was error. In client
77 it is not called but in server, I think, it must be called.
78 When implementing this check that all commands handle the
79 situation correctly when it is called as pending command
80 (it should most likely check that cmd->pending == TRUE/FALSE).
82 o TODO in notify types (packet_receive.c):
84 o SERVER_SIGNOFF notify type is not implemented
86 o Packet processing can be made faster. All packet function in the
87 packet_receive.c has same prototypes. Instead of calling those from
88 huge switch() make a table of callback functions that can be called
89 directly by the packet type.
91 o DNS/IP lookup blocks the server. This must be fixed. Check the
92 resolver stuff (resolver(3), resolver(5)). Either we have to do the
93 own resolver stuff (through scheduler, if possible without writing
94 too much own stuff) or use threads.
96 o Acceptance of incoming connections (client and server connections)
97 should be checked before key exchange protocol. Currently it is
98 checked at the authentication phase after KE, that is ok, but it should
99 be checked before starting KE, as well.
101 o Server says that it is able to listen on multiple ports but currently
102 that is bogus. It can, but internals are for single server.
104 o Protocol execution timeouts are hard coded, should be configurable.
106 o IP address fields in configuration file should accept mask format
107 as well, IP/MASK, and not just plain IP.
109 o Connection classes should be actually implemented in serverconfig.c.
110 They can be defined but they are totally ignored currently.
113 TODO In SILC Libraries
114 ======================
116 o Implement PFS (Perfect Forward Secrecy) flag in SKE (and in client and
117 server, actually). If PFS is set, re-key must cause new key exchange.
118 This is required by the SILC protocol.
120 o Re-key in general is actually missing (from everywhere) and must be done.
122 o Compression routines are missing. The protocol supports packet
123 compression thus it must be implemented. SILC Comp API must be
124 defined. zlib package is already included into the lib dir (in CVS,
125 not in distribution), but it is not used yet, and it requires some
126 tweaking on the Makefiles (we want static lib not shared).
128 o Rewrite the task system. I made it too complex and too "neat" and
129 it really should be rewritten. We don't need priorities really, one
130 priority is enough. This will simplify a lot the task system.
132 o SIM support for SILC PKCS API needs to made so that they could be
133 used as SIM's. At the same time some work is required on prime
134 generation as the way it is done now sucks. Read from code for
137 o Random Number Generator needs some tweaking. Reading /dev/random may
138 block resulting slow initialization of RNG. Some other things in the
139 RNG may block as well. Also, I have some pending changes to the RNG
140 that needs to be commited (from Schneier's Yarrow-160 paper). They
141 should make the RNG even better.
143 o Scheduler needs to be analyzed on high load as it might be unfair
144 towards select() because it may run timeout tasks before select() and
145 after select(). If it is found to be unfair the timeout task running
146 before select() should probably be removed.
149 TODO in the protocol before SILC 0.x
150 ====================================
152 o New commands and features in the commands
153 (draft-riikonen-silc-spec-xx.txt):
155 o Define GETKEY command to fetch the public key of a server
156 and/or a client in the SILC Network.
157 o Define SENDKEY command to send your public key to a client
158 in the network. Sending to the server must not be done due
159 to various security reasons (the server must not trust the
160 public keys blindly without third party verification; that's
161 why SENDKEY is not for servers).
162 o Define AWAY command to set the indication flag whether the
163 client is present or not. Do not save the away message to the
165 o Define the channel founder property to be permanent locally in
166 the server so that channel founder can regain its rights even
167 if it disconnects from the server. Thus, define a new command
168 or channel user mode that can be used to set the channel founder
169 passphrase or public key that can be used in the authentication
170 when regaining the founder rights.
172 o New packets and features in the packets
173 (draft-riikonen-silc-pp-xx.txt):
175 o Define the Private Message packet to include private message
176 flags and define the flags. The flags could indicate whether
177 the message is, for example autoreply or the receiver should not
178 reply to the private messages. What other flags?
179 o Define the Channel Message packet to include channel message
180 flags and define the flags. Actually the flags should be same
181 as for the private message flags. This way we can implement
182 for example the CTCP style ACTION (/ME command) messages.
184 o New features in the KE/auth protocol
185 (draft-riikonen-silc-ke-auth-xx.txt):
187 o Define group exchange support for the SKE so that the SKE
188 could be performed among more than two entities. This is not
189 a showstopper and may be defined later.
195 o Pthreads support. A lot of problems are solved with server (and with
196 client as well) if we add pthread support. We can forget things such
197 as non-blocking connecting etc, and we can do things such as DNS/IP
198 lookups async. The server itself also benefits great deal from
199 threads, especially from performance point of view.
201 But, this is not a small task and almost entire SILC Library has to
202 be made re-entrant. Own API is probably added for the threads support
203 to make changes in the future as painless as possible. So the API
204 would have things like silc_mutex_lock, silc_mutex_unlock and
207 o X.509 certificate support. SILC protocol supports certificates and
208 it would be great to have support for them. This is a big task as
209 support has to be made for ASN.1 as well. I've looked into OpenSSL
210 package as it has X.509 certificate support (and ASN.1 as well).
211 The code does not look very good to my eye but it has some potentials.
212 This should be looked at more closely.
214 Naturally own SILC Certificate API has to be defined regardles what
215 the actual X.509 library is (OpenSSL X.509 or something else). Other
216 choice is to write own X.509 library but I'm not going to do it -
217 I can help to migrate the OpenSSL X.509 into SILC and I can help if
218 someone would like to write the X.509 library - but I'm not going
219 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
222 o SSH2 public keys support. Maybe - not really needed but could be
223 nice as SSH is widely used all over the place. SILC Protocol
224 supports SSH2 public keys.
226 o Cipher optimizations (asm, that this) at least for i386 would be nice.