TODO/bugs In SILC Client Library
================================
- o Three clients, two with same nickname, one nick, other nick@host,
- the nick quits and rejoins channel it becomes nick@host for the third
- client. Both shows nick@host in the third client. This is a bug.
-
o The PRIVATE_MESSAGE_KEY packet is not handled (it is implemented
though). This should be added and perhaps new client operation
should be added to notify application that it was received and
set the key only if application wishes to set (accept the key) it
(Do this to 1.0).
- o Additions to do after protocol version 1.1:
+ o Remove conn->current_channel.
- o Fix the NICK_CHANGE notify handling not to create new entry
- for the changed client, but take the nickname from the notify
- (removes need for resolving as well). Protocol TODO entry 3.
+ o Additions to do after protocol version 1.1:
o Add support for list of errors in command replies. Protocol
TODO entry 1.
TODO/bugs In SILC Server
========================
- o KICKing doesn't work.
-
o Configuration file additions (Do this to 0.8.x):
o Add incoming connection frequency, incoming connection frequency
for single IP address, key exchange frequency, key exchange
frequency for single IP. Add also frequency base.
- o Add rehashing support.
-
o If server send CUMODE_CHANGE notify (like setting founder) to router
and router does not have founder on channel (founder is left or there's
no founder on channel at all), the router will accept the server's
o JOIN (check that joining is allowed)
o SIGNOFF (maybe should check that notifier owns the client)
- o KILLED (check that killling is allowed (Protocol TODO #13))
o Backup router related issues (Fix this to 1.0):
o WIN32 silc_net_create_connection_async does not work the same way
than on Unix. Do it with threads on WIN32. The function works but
- is not actually async currently.
-
- o EPOC specific additions/changes required:
-
- o lib/silcutil/epoc routines missing or not completed.
+ is not actually async currently (Fix this to 1.0).
TODO in Toolkit Documentation
=============================
Stuff that needs to be done in order to complete the Tooolkit Reference
-Manual.
+Manual (Do these to 0.9 and 1.0).
o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h.
o ROBOdoc documenting missing from lib/silcutil/silcfileutil.h.
- o ROBOdoc documenting missing from lib/silcutil/silcutil.h.
-
o ROBOdoc documenting missing from lib/silccrypt/silchash.h.
o ROBOdoc documenting missing from lib/silccrypt/silccipher.h.
*after* sending successfully found entries (this way receiver may
ignore them). To be included in protocol version 1.1.
- 3. Define the NICK_CHANGE notify to send the changed nickname as a new
- third argument. This will make the NICK_CHANGE notify handling easier
- in the receiver's end (client primarily) since it removes the
- requirement that receiver must resolve (using IDENTIFY or WHOIS) the
- new Client ID received in the notify (because of the new nickname is
- unknown). To be included in protocol version 1.1.
-
4. Add "request parameters" or similar to the WHOIS command, which can
be used to request various parameters (something not returned by
standard WHOIS command) about clients (info that could be fetched
new features without always making the command incompatible to previous
version. To be included in protocol version 1.1.
- 5. Inviting and banning by public key should be made possible. To be
- included in protocol version 1.x.
-
- 6. Add perhaps SILENCE_USERS, SILENCE_OPERS channel user modes which
- can be used to silence (moderate) normal users and opers (this set
- only by founder). To be included in protocol version 1.1.
-
- 7. Channel Message Payload needs slight redesining to include the IV
- field to the MAC generation of the payload. It is authenticated
- by the packet's MAC but not by the payload's MAC. Since the IV
- belongs to the payload, its integrity should be protected by the
- payload MAC and not alone by packet MAC. To be included in protocol
- version 1.1.
-
- 8. Remove the administrative commands from the protocol all together.
- It does not make sense for the protocol to define how a server is
- reconnected or shutdown, since they are implementation and
- configuration issues. Besides protocol provides only limited set of
- administrative commands and cannot define all that one could imagine.
- To be included in protocol version 1.1.
-
- 9. Add SILC_MESAGE_FLAG_REPLY for being other side to the
- SILC_MESSAGE_FLAG_REQUEST. Add generic SILC_MESSAGE_FLAG_DATA, which
- can include generic payload, which can include generic data. The
- payload definition is left out for now. To be included in protocol
- version 1.1.
-
- 10. Check command reply error status types in various commands,
- specifically NO_FOPRIV is missing from many commands. To be
- included in protocol version 1.1.
-
- 11. Change the wording in Private Message Key Payload definition to
- describe the problems of trusting the payload, and to indicate that
- the receiver may not accept the key in the payload, and to describe
- other means of distributing a key.
-
- 13. Add the killer's client ID to the KILLED notify. To be included in
- protocol version 1.1.
-
- 14. The length of Arguments Num field in Notify Payload and Command
- Payload enforces that total of 256 arguments can be associated
- to a such payload. However, command-xx draft specified much higher
- values, and these should be fixed.
+ 17. Cell wide channel founder support, and permanent channels when
+ founder mode set.
+
+ 18. Describe the SSH public key, X509, OpenPGP and SPKI certificates
+ encoding format in SKE (from their respective definitions).
+
+ o Inviting and banning by public key should be made possible. To be
+ included in protocol version 1.2.
+
+ o UTF-8 support/requirement for nicknames & channel names. UTF-8 support
+ in terminals and OS's are so hazy that this matter is left for
+ consideration in next version of the protocol (1.2). For good UTF-8
+ reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
+ What should CLI application do if it receives nickname that it cannot
+ display without messing up the terminal? If UTF-8 is mandatory in
+ SILC then SILC clients cannot be allowed to start on terminals that do
+ not support UTF-8 (which renders 98% of users unable to use CLI SILC
+ app without hacking their environment). See also site
+ http://gratrix.net/unicode/
projects / silc.git / blobdiff