1 TODO/bugs in Irssi SILC client
2 ==============================
4 o Does not show ops and normal users on JOIN correctly, perhaps some
5 theme issue (Fix this to 0.8.x).
7 o /cumode for unknown nick does not give any error message (Fix this to
11 TODO/bugs In SILC Client Library
12 ================================
14 o The PRIVATE_MESSAGE_KEY packet is not handled (it is implemented
15 though). This should be added and perhaps new client operation
16 should be added to notify application that it was received and
17 set the key only if application wishes to set (accept the key) it
20 o Additions to do after protocol version 1.1:
22 o Fix the NICK_CHANGE notify handling not to create new entry
23 for the changed client, but take the nickname from the notify
24 (removes need for resolving as well). Protocol TODO entry 3.
26 o Add support for list of errors in command replies. Protocol
30 TODO/bugs In SILC Server
31 ========================
33 o Configuration file additions (Do this to 0.8.x):
35 o Add incoming connection frequency, incoming connection frequency
36 for single IP address, key exchange frequency, key exchange
37 frequency for single IP. Add also frequency base.
39 o If server send CUMODE_CHANGE notify (like setting founder) to router
40 and router does not have founder on channel (founder is left or there's
41 no founder on channel at all), the router will accept the server's
42 founder mode change, even though it perhaps should not do that (Fix
45 o The router should check for validity of received notify packets from
46 routers (fix this to 0.9). Following NOTIFYs needs to be verified:
48 o JOIN (check that joining is allowed)
49 o SIGNOFF (maybe should check that notifier owns the client)
50 o KILLED (check that killling is allowed (Protocol TODO #13))
52 o Backup router related issues (Fix this to 1.0):
54 o Channel user mode changes are notified unnecessarely when
55 switching to backup router on router crash.
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 (Fix this to 1.0).
64 o Lots of statistics updating is missing around the server.
66 o If client's public key is saved in the server (and doing public key
67 authentication) then the hostname and the username information could
68 be taken from the public key. Should be a configuration option!
71 TODO/bugs In SILC Libraries
72 ===========================
74 o WIN32 silc_net_create_connection_async does not work the same way
75 than on Unix. Do it with threads on WIN32. The function works but
76 is not actually async currently (Fix this to 1.0).
79 TODO in Toolkit Documentation
80 =============================
82 Stuff that needs to be done in order to complete the Tooolkit Reference
83 Manual (Do these to 0.9 and 1.0).
85 o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h.
87 o ROBOdoc documenting missing from lib/silcutil/silcdlist.h.
89 o ROBOdoc documenting missing from lib/silcutil/silcfileutil.h.
91 o ROBOdoc documenting missing from lib/silccrypt/silchash.h.
93 o ROBOdoc documenting missing from lib/silccrypt/silccipher.h.
95 o ROBOdoc documenting missing from lib/silccrypt/silcpkcs.h.
97 o Write "Programming with Toolkit" document, describing how to build
98 Toolkit, how the build system works, where is everything, how
99 new (external) projects can be glued into Toolkit (use irssi as an
100 example), and how external projects can use Toolkit without gluing into
101 it (how to link etc), debugging, architecture, types, etc.
103 o Write "Platform Implementations" document to describe what platforms
104 Toolkit support, what has been implemented, what has not been, what
105 works differently etc.
108 TODO in SILC Protocol
109 =====================
111 Current protocol version is 1.0. However, it is far from being perfect,
112 and needs to include additional features. Following protocol TODO entries
113 describe new stuff to be added to protocol versions 1.x.
115 1. Re-define the Status Payload: it is now 16 bits, split it into two
116 8 bits fields. First field includes status types from 0 - 9 and
117 10 - n *if* it is not an list of errors. If it is list of errors then
118 the first field includes 1, 2 and/or 3, and the second field includes
119 the error status 10 - n. This way it is possible to send multiple
120 errors (list of errors) and we have a way to tell the receiver that
121 there will be other errors as well. The second field is used only
122 if there is list of errors. If normal status, or normal (single)
123 error status the second field is set to zero, and must be ignored.
124 Hence, the status works same way as now except for list of errors.
125 To be included in protocol version 1.1.
127 2. Define that WHOIS and IDENTIFY commands must send list of errors
128 if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
129 requested and was not found. Each unfound entry must cause an error
130 command reply to the sender. Also define that errors must be sent
131 *after* sending successfully found entries (this way receiver may
132 ignore them). To be included in protocol version 1.1.
134 3. Define the NICK_CHANGE notify to send the changed nickname as a new
135 third argument. This will make the NICK_CHANGE notify handling easier
136 in the receiver's end (client primarily) since it removes the
137 requirement that receiver must resolve (using IDENTIFY or WHOIS) the
138 new Client ID received in the notify (because of the new nickname is
139 unknown). To be included in protocol version 1.1.
141 4. Add "request parameters" or similar to the WHOIS command, which can
142 be used to request various parameters (something not returned by
143 standard WHOIS command) about clients (info that could be fetched
144 even from clients). Additional specification (or appendix) should
145 be done to define the payload and the parameters. It could be used
146 to make the WHOIS command support various search conditions as well.
147 This would be the way to extend the WHOIS command to support various
148 new features without always making the command incompatible to previous
149 version. To be included in protocol version 1.1.
151 5. Inviting and banning by public key should be made possible. To be
152 included in protocol version 1.x.
154 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
155 can be used to silence (moderate) normal users and opers (this set
156 only by founder). To be included in protocol version 1.1.
158 7. Channel Message Payload needs slight redesining to include the IV
159 field to the MAC generation of the payload. It is authenticated
160 by the packet's MAC but not by the payload's MAC. Since the IV
161 belongs to the payload, its integrity should be protected by the
162 payload MAC and not alone by packet MAC. To be included in protocol
165 8. Remove the administrative commands from the protocol all together.
166 It does not make sense for the protocol to define how a server is
167 reconnected or shutdown, since they are implementation and
168 configuration issues. Besides protocol provides only limited set of
169 administrative commands and cannot define all that one could imagine.
170 To be included in protocol version 1.1.
172 9. Add SILC_MESAGE_FLAG_REPLY for being other side to the
173 SILC_MESSAGE_FLAG_REQUEST. Add generic SILC_MESSAGE_FLAG_DATA, which
174 can include generic payload, which can include generic data. The
175 payload definition is left out for now. To be included in protocol
178 10. Check command reply error status types in various commands,
179 specifically NO_FOPRIV is missing from many commands. To be
180 included in protocol version 1.1.
182 11. Change the wording in Private Message Key Payload definition to
183 describe the problems of trusting the payload, and to indicate that
184 the receiver may not accept the key in the payload, and to describe
185 other means of distributing a key.
187 13. Add the killer's client ID to the KILLED notify. To be included in
188 protocol version 1.1.
190 14. The length of Arguments Num field in Notify Payload and Command
191 Payload enforces that total of 256 arguments can be associated
192 to a such payload. However, command-xx draft specified much higher
193 values, and these should be fixed.
195 15. The LEAVE command reply should return the Channel ID of the channel