1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Fix the silc_channels_join to parse the command like, with fe.
5 silc_parse_command_line, because currently it ignores all options,
6 including passphrase which makes autojoin impossible to +a channels.
7 Other important options are ignored too.
9 o Add local command to switch the channel's private key when channel has
10 several private keys. Currently sending channel messages with many
11 keys is not possible because changing the key is not possible by the
14 o /cumode for unknown nick does not give any error message.
17 TODO/bugs In SILC Client Library
18 ================================
20 o The PRIVATE_MESSAGE_KEY packet is not handled (it is implemented
21 though). This should be added and perhaps new client operation
22 should be added to notify application that it was received and
23 set the key only if application wishes to set (accept the key) it.
25 o Additions to do after protocol version 1.1:
27 o Fix the NICK_CHANGE notify handling not to create new entry
28 for the changed client, but take the nickname from the notify
29 (removes need for resolving as well). Protocol TODO entry 3.
31 o Add support for list of errors in command replies. Protocol
35 TODO/bugs In SILC Server
36 ========================
38 o Configuration file additions:
40 o Add incoming connection frequency, incoming connection frequency
41 for single IP address, key exchange frequency, key exchange
42 frequency for single IP. Add also frequency base.
44 o Add hashed passwords to config file.
46 o Add rehashing support.
48 o If server send CUMODE_CHANGE notify (like setting founder) to router
49 and router does not have founder on channel (founder is left or there's
50 no founder on channel at all), the router will accept the server's
51 founder mode change, even though it perhaps should not do that.
53 o The router should check for validity of received notify packets from
54 servers (after all buggy servers may send notify that is actually
55 something that should have not been sent).
57 o Add a timeout to handling incoming JOIN commands. It should be
58 enforced that JOIN command is executed only once in a second or two
59 seconds. Now it is possible to accept n incoming JOIN commands
60 and process them without any timeouts. THis must be employed because
61 each JOIN command will create and distribute the new channel key
62 to everybody on the channel.
64 o Backup router related issues
66 o Channel user mode changes are notified unnecessarely when
67 switching to backup router on router crash.
69 o Lots of statistics updating is missing around the server.
71 o If client's public key is saved in the server (and doing public key
72 authentication) then the hostname and the username information could
73 be taken from the public key. Should be a configuration option!
76 TODO/bugs In SILC Libraries
77 ===========================
79 o WIN32 silc_net_create_connection_async does not work the same way
80 than on Unix. Do it with threads on WIN32. The function works but
81 is not actually async currently.
83 o EPOC specific additions/changes required:
85 o lib/silcutil/epoc routines missing or not completed.
88 TODO in Toolkit Documentation
89 =============================
91 Stuff that needs to be done in order to complete the Tooolkit Reference
94 o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h.
96 o ROBOdoc documenting missing from lib/silcutil/silcdlist.h.
98 o ROBOdoc documenting missing from lib/silcutil/silcfileutil.h.
100 o ROBOdoc documenting missing from lib/silcutil/silcutil.h.
102 o ROBOdoc documenting missing from lib/silccrypt/silchash.h.
104 o ROBOdoc documenting missing from lib/silccrypt/silccipher.h.
106 o ROBOdoc documenting missing from lib/silccrypt/silcpkcs.h.
108 o Write "Programming with Toolkit" document, describing how to build
109 Toolkit, how the build system works, where is everything, how
110 new (external) projects can be glued into Toolkit (use irssi as an
111 example), and how external projects can use Toolkit without gluing into
112 it (how to link etc), debugging, architecture, types, etc.
114 o Write "Platform Implementations" document to describe what platforms
115 Toolkit support, what has been implemented, what has not been, what
116 works differently etc.
119 TODO in SILC Protocol
120 =====================
122 Current protocol version is 1.0. However, it is far from being perfect,
123 and needs to include additional features. Following protocol TODO entries
124 describe new stuff to be added to protocol versions 1.x.
126 1. Re-define the Status Payload: it is now 16 bits, split it into two
127 8 bits fields. First field includes status types from 0 - 9 and
128 10 - n *if* it is not an list of errors. If it is list of errors then
129 the first field includes 1, 2 and/or 3, and the second field includes
130 the error status 10 - n. This way it is possible to send multiple
131 errors (list of errors) and we have a way to tell the receiver that
132 there will be other errors as well. The second field is used only
133 if there is list of errors. If normal status, or normal (single)
134 error status the second field is set to zero, and must be ignored.
135 Hence, the status works same way as now except for list of errors.
136 To be included in protocol version 1.1.
138 2. Define that WHOIS and IDENTIFY commands must send list of errors
139 if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
140 requested and was not found. Each unfound entry must cause an error
141 command reply to the sender. Also define that errors must be sent
142 *after* sending successfully found entries (this way receiver may
143 ignore them). To be included in protocol version 1.1.
145 3. Define the NICK_CHANGE notify to send the changed nickname as a new
146 third argument. This will make the NICK_CHANGE notify handling easier
147 in the receiver's end (client primarily) since it removes the
148 requirement that receiver must resolve (using IDENTIFY or WHOIS) the
149 new Client ID received in the notify (because of the new nickname is
150 unknown). To be included in protocol version 1.1.
152 4. Add "request parameters" or similar to the WHOIS command, which can
153 be used to request various parameters (something not returned by
154 standard WHOIS command) about clients (info that could be fetched
155 even from clients). Additional specification (or appendix) should
156 be done to define the payload and the parameters. It could be used
157 to make the WHOIS command support various search conditions as well.
158 This would be the way to extend the WHOIS command to support various
159 new features without always making the command incompatible to previous
160 version. To be included in protocol version 1.1.
162 5. Inviting and banning by public key should be made possible. To be
163 included in protocol version 1.x.
165 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
166 can be used to silence (moderate) normal users and opers (this set
167 only by founder). To be included in protocol version 1.1.
169 7. Channel Message Payload needs slight redesining to include the IV
170 field to the MAC generation of the payload. It is authenticated
171 by the packet's MAC but not by the payload's MAC. Since the IV
172 belongs to the payload, its integrity should be protected by the
173 payload MAC and not alone by packet MAC. To be included in protocol
176 8. Remove the administrative commands from the protocol all together.
177 It does not make sense for the protocol to define how a server is
178 reconnected or shutdown, since they are implementation and
179 configuration issues. Besides protocol provides only limited set of
180 administrative commands and cannot define all that one could imagine.
181 To be included in protocol version 1.1.
183 9. Add SILC_MESAGE_FLAG_REPLY for being other side to the
184 SILC_MESSAGE_FLAG_REQUEST. Add generic SILC_MESSAGE_FLAG_DATA, which
185 can include generic payload, which can include generic data. The
186 payload definition is left out for now. To be included in protocol
189 10. Check command reply error status types in various commands,
190 specifically NO_FOPRIV is missing from many commands. To be
191 included in protocol version 1.1.
193 11. Change the wording in Private Message Key Payload definition to
194 describe the problems of trusting the payload, and to indicate that
195 the receiver may not accept the key in the payload, and to describe
196 other means of distributing a key.
198 13. Add the killer's client ID to the KILLED notify. To be included in
199 protocol version 1.1.
201 14. The length of Arguments Num field in Notify Payload and Command
202 Payload enforces that total of 256 arguments can be associated
203 to a such payload. However, command-xx draft specified much higher
204 values, and these should be fixed.