4 o We should replace all short, int, long, unsigned short, unsigned int,
5 unsigned long with some pre-defined datatypes that really are what
6 we want on all platforms. int16, uint16, int32, uint32 etc. are
7 what we could use or maybe SilcInt16, SilcUInt16 etc. Also, boolean
8 datatype should be defined.
11 TODO In SILC Client Library
12 ===========================
14 o Client library crashes if for example server timeouts protocol
15 execution and disconnects the client. The client, on the other hand
16 may still assume that the connection is active, even after receiving
17 the EOF. Reason for this is that the clien library does not handle
18 the SilcSocketConnection reference counter at all. This must be
21 o I guess, public key authentication (when connecting to a server)
22 is not working currently. It is just matter of loading the keys
23 from file and using them (see corresponding code in server).
25 o Add client library parameters or options that handle what kind of
26 messages the library should print out (using `say' client operation,
27 for example) and what is left for the application to print. The
28 appliation could for example set that it handles all command printing
29 but all error printing should be handled by the library, etc...
30 This is not a showstopper.
32 o Input line on UI is buggy. Cursor movement etc bugs. Too lazy to
39 o TODO in commands (command.c and command_reply.c):
41 o RESTART is not implemented
42 o In servers all command reply funtions should still call the
43 pending command reply even if the reply was error. In client
44 it is not called but in server, I think, it must be called.
45 When implementing this check that all commands handle the
46 situation correctly when it is called as pending command
47 (it should most likely check that cmd->pending == TRUE/FALSE).
49 o TODO in notify types (packet_receive.c):
51 o SERVER_SIGNOFF notify type is not implemented
53 o Acceptance of incoming connections (client and server connections)
54 should be checked before key exchange protocol. Currently it is
55 checked at the authentication phase after KE, that is ok, but it should
56 be checked before starting KE, as well.
58 o DNS/IP lookup blocks the server. This must be fixed. Check the
59 resolver stuff (resolver(3), resolver(5)). Either we have to do the
60 own resolver stuff (through scheduler, if possible without writing
61 too much own stuff) or use threads.
63 o Packet processing can be made faster. All packet function in the
64 packet_receive.c has same prototypes. Instead of calling those from
65 huge switch() make a table of callback functions that can be called
66 directly by the packet type.
68 o Server says that it is able to listen on multiple ports but currently
69 that is bogus. It can, but internals are for single server.
71 o Protocol execution timeouts are hard coded, should be configurable.
73 o IP address fields in configuration file should accept mask format
74 as well, IP/MASK, and not just plain IP.
76 o Connection classes should be actually implemented in serverconfig.c.
77 They can be defined but they are totally ignored currently.
80 TODO In SILC Libraries
81 ======================
83 o Implement PFS (Perfect Forward Secrecy) flag in SKE (and in client and
84 server, actually). If PFS is set, re-key must cause new key exchange.
85 This is required by the SILC protocol.
87 o Re-key in general is actually missing (from everywhere) and must be done.
89 o Compression routines are missing. The protocol supports packet
90 compression thus it must be implemented. SILC Comp API must be
91 defined. zlib package is already included into the lib dir (in CVS,
92 not in distribution), but it is not used yet, and it requires some
93 tweaking on the Makefiles (we want static lib not shared).
95 o Rewrite the task system. I made it too complex and too "neat" and
96 it really should be rewritten. We don't need priorities really, one
97 priority is enough. This will simplify a lot the task system.
99 o SIM support for SILC PKCS API needs to made so that they could be
100 used as SIM's. At the same time some work is required on prime
101 generation as the way it is done now sucks. Read from code for
104 o Random Number Generator needs some tweaking. Reading /dev/random may
105 block resulting slow initialization of RNG. Some other things in the
106 RNG may block as well. Also, I have some pending changes to the RNG
107 that needs to be commited (from Schneier's Yarrow-160 paper). They
108 should make the RNG even better.
111 TODO in the protocol before SILC 0.x
112 ====================================
114 o New commands and features in the commands
115 (draft-riikonen-silc-spec-xx.txt):
117 o Define GETKEY command to fetch the public key of a server
118 and/or a client in the SILC Network.
119 o Define SENDKEY command to send your public key to a client
120 in the network. Sending to the server must not be done due
121 to various security reasons (the server must not trust the
122 public keys blindly without third party verification; that's
123 why SENDKEY is not for servers).
129 o Pthreads support. A lot of problems are solved with server (and with
130 client as well) if we add pthread support. We can forget things such
131 as non-blocking connecting etc, and we can do things such as DNS/IP
132 lookups async. The server itself also benefits great deal from
133 threads, especially from performance point of view.
135 But, this is not a small task and almost entire SILC Library has to
136 be made re-entrant. Own API is probably added for the threads support
137 to make changes in the future as painless as possible. So the API
138 would have things like silc_mutex_lock, silc_mutex_unlock and
141 o X.509 certificate support. SILC protocol supports certificates and
142 it would be great to have support for them. This is a big task as
143 support has to be made for ASN.1 as well. I've looked into OpenSSL
144 package as it has X.509 certificate support (and ASN.1 as well).
145 The code does not look very good to my eye but it has some potentials.
146 This should be looked at more closely.
148 Naturally own SILC Certificate API has to be defined regardles what
149 the actual X.509 library is (OpenSSL X.509 or something else). Other
150 choice is to write own X.509 library but I'm not going to do it -
151 I can help to migrate the OpenSSL X.509 into SILC and I can help if
152 someone would like to write the X.509 library - but I'm not going
153 to start writing one myself. Anyhow, the OpenSSL X.509 lib should
156 o SSH2 public keys support. Maybe - not really needed but could be
157 nice as SSH is widely used all over the place. SILC Protocol
158 supports SSH2 public keys.
160 o Cipher optimizations (asm, that this) at least for i386 would be nice.