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 version handling, to allow, disallow certain versions to
43 o Add incoming connection frequency, incoming connection frequency
44 for single IP address, key exchange frequency, key exchange
45 frequency for single IP. Add also frequency base.
47 o Add hashed passwords to config file.
49 o Add rehashing support.
51 o If server send CUMODE_CHANGE notify (like setting founder) to router
52 and router does not have founder on channel (founder is left or there's
53 no founder on channel at all), the router will accept the server's
54 founder mode change, even though it perhaps should not do that.
56 o The router should check for validity of received notify packets from
57 servers (after all buggy servers may send notify that is actually
58 something that should have not been sent).
60 o Add a timeout to handling incoming JOIN commands. It should be
61 enforced that JOIN command is executed only once in a second or two
62 seconds. Now it is possible to accept n incoming JOIN commands
63 and process them without any timeouts. THis must be employed because
64 each JOIN command will create and distribute the new channel key
65 to everybody on the channel.
67 o Backup router related issues
69 o Channel user mode changes are notified unnecessarely when
70 switching to backup router on router crash.
72 o Lots of statistics updating is missing around the server.
74 o If client's public key is saved in the server (and doing public key
75 authentication) then the hostname and the username information could
76 be taken from the public key. Should be a configuration option!
79 TODO/bugs In SILC Libraries
80 ===========================
82 o WIN32 silc_net_create_connection_async does not work the same way
83 than on Unix. Do it with threads on WIN32. The function works but
84 is not actually async currently.
86 o EPOC specific additions/changes required:
88 o lib/silcutil/epoc routines missing or not completed.
91 TODO in Toolkit Documentation
92 =============================
94 Stuff that needs to be done in order to complete the Tooolkit Reference
97 o Lots of ROBOdoc header formatting is undone in lib/silcutil, and
100 o Write "Programming with Toolkit" document, describing how to build
101 Toolkit, how the build system works, where is everything, how
102 new (external) projects can be glued into Toolkit (use irssi as an
103 example), and how external projects can use Toolkit without gluing into
104 it (how to link etc), debugging, architecture, types, etc.
106 o Write "Platform Implementations" document to describe what platforms
107 Toolkit support, what has been implemented, what has not been, what
108 works differently etc.
111 TODO in SILC Protocol
112 =====================
114 Current protocol version is 1.0. However, it is far from being perfect,
115 and needs to include additional features. Following protocol TODO entries
116 describe new stuff to be added to protocol versions 1.x.
118 1. Re-define the Status Payload: it is now 16 bits, split it into two
119 8 bits fields. First field includes status types from 0 - 9 and
120 10 - n *if* it is not an list of errors. If it is list of errors then
121 the first field includes 1, 2 and/or 3, and the second field includes
122 the error status 10 - n. This way it is possible to send multiple
123 errors (list of errors) and we have a way to tell the receiver that
124 there will be other errors as well. The second field is used only
125 if there is list of errors. If normal status, or normal (single)
126 error status the second field is set to zero, and must be ignored.
127 Hence, the status works same way as now except for list of errors.
128 To be included in protocol version 1.1.
130 2. Define that WHOIS and IDENTIFY commands must send list of errors
131 if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
132 requested and was not found. Each unfound entry must cause an error
133 command reply to the sender. Also define that errors must be sent
134 *after* sending successfully found entries (this way receiver may
135 ignore them). To be included in protocol version 1.1.
137 3. Define the NICK_CHANGE notify to send the changed nickname as a new
138 third argument. This will make the NICK_CHANGE notify handling easier
139 in the receiver's end (client primarily) since it removes the
140 requirement that receiver must resolve (using IDENTIFY or WHOIS) the
141 new Client ID received in the notify (because of the new nickname is
142 unknown). To be included in protocol version 1.1.
144 4. Add "request parameters" or similar to the WHOIS command, which can
145 be used to request various parameters (something not returned by
146 standard WHOIS command) about clients (info that could be fetched
147 even from clients). Additional specification (or appendix) should
148 be done to define the payload and the parameters. It could be used
149 to make the WHOIS command support various search conditions as well.
150 This would be the way to extend the WHOIS command to support various
151 new features without always making the command incompatible to previous
152 version. To be included in protocol version 1.1.
154 5. Inviting and banning by public key should be made possible. To be
155 included in protocol version 1.x.
157 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
158 can be used to silence (moderate) normal users and opers (this set
159 only by founder). To be included in protocol version 1.1.
161 7. Channel Message Payload needs slight redesining to include the IV
162 field to the MAC generation of the payload. It is authenticated
163 by the packet's MAC but not by the payload's MAC. Since the IV
164 belongs to the payload, its integrity should be protected by the
165 payload MAC and not alone by packet MAC. To be included in protocol
168 8. Remove the administrative commands from the protocol all together.
169 It does not make sense for the protocol to define how a server is
170 reconnected or shutdown, since they are implementation and
171 configuration issues. Besides protocol provides only limited set of
172 administrative commands and cannot define all that one could imagine.
173 To be included in protocol version 1.1.
175 9. Add SILC_MESAGE_FLAG_REPLY for being other side to the
176 SILC_MESSAGE_FLAG_REQUEST. Add generic SILC_MESSAGE_FLAG_DATA, which
177 can include generic payload, which can include generic data. The
178 payload definition is left out for now. To be included in protocol
181 10. Check command reply error status types in various commands,
182 specifically NO_FOPRIV is missing from many commands. To be
183 included in protocol version 1.1.
185 11. Change the wording in Private Message Key Payload definition to
186 describe the problems of trusting the payload, and to indicate that
187 the receiver may not accept the key in the payload, and to describe
188 other means of distributing a key.
190 13. Add the killer's client ID to the KILLED notify. To be included in
191 protocol version 1.1.