that the user has. And a local command to dump the contents of the
public key to the screen. Something like LISTKEYS, SHOWKEY...
- o The JOIN command's HELP is generated from Irssi IRCs JOIN help and
- the syntax is not same in SILC. This must be fixed. Most likely
- we must forget the Irssi's JOIN command and mimic it to get our
- required syntax for it too.
-
o We should get rid of the clientconfig.[ch] in Irssi SILC and move the
cipher, hash, hmac and pkcs configuration to the Irssi SILC's config
file.
TODO/bugs In SILC Client Library
================================
- o JOIN command's argument handling is buggy. See the XXX in the code.
+ 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.
+ o should /nick nick and /nick Nick cause the Nick to be Nick@host becase
+ it used to be nick??
-TODO/bugs In SILC Server
-========================
+ o When changing own nickname and there exists a same nickname the library
+ can give the client now nickname in format nick@host. This is new
+ behaviour and maybe should be removed. The changer should always
+ get the one it wants and not have the formatted nickname.
- o Implement the <founder auth> and founder privileges gaining to
- the JOIN command. This will bypass invite-only mode as well for
- the client who got the founder mode during JOIN.
+ o Remove the command destructor all together from the client, it is
+ not needed and its usage is buggy when the context is registered
+ to multiple pending commands.
- o After backup resume protocol the TOPIC_SET was not handled correctly
- by all (unknown Channel ID).
+ o Additions to do after protocol version 1.1:
- o Channel user mode changes are notified unnecessarely when switching
- to backup router on router crash.
+ 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 Change the server to connect to another server from low ports (706)
- and not from high ports. Currently we cannot do incoming connection
- checking by remote port because the port is not fixed.
+ o Add support for list of errors in command replies. Protocol
+ TODO entry 1.
- o Announcements are incomplete: channel topics are not announced,
- user modes (UMODE) are not announced.
- o If client's public key is saved in the server (and doing public key
- authentication) then the hostname and the username information could
- be taken from the public key. Should be a configuration option!
+TODO/bugs In SILC Server
+========================
+
+ o strerror messages from premature EOF's to signoff messages.
+ (add perhaps a socket error thingy to SilcSockeConnection).
+
+ o Backup router related issues
+
+ o Channel user mode changes are notified unnecessarely when
+ switching to backup router on router crash.
o Add a timeout to handling incoming JOIN commands. It should be
enforced that JOIN command is executed only once in a second or two
each JOIN command will create and distribute the new channel key
to everybody on the channel.
- o Optimize the WHOIS and IDENTIFY commands to somehow check whether the
- requested clients are on some channel that the server knows about. If
- this is the case then the request is not needed to be forwarded to the
- router. One specific optimization could be done with JOIN command.
- If the previous command to the WHOIS and IDENTIFY commands are JOIN
- command (from the client) it can be expected (though it must be
- verified) that the client is resolving the users on the channel it just
- joined. If server has done this once there is really no reason to
- resolve it twice (from the router), it can reply directly back with
- the information it knows. This is because the server would (will)
- receive notifications from the router for users that are on a local
- channel.
-
- The same is with whowas command. Actually with all these commands
- it should be checked also whether the requested information is local.
- If it is, there is no reason to send it to the router, since the server
- knows it best.
-
o New configuration file format must be added. The new one will be
done using the dotconf config library (lib/dotconf). The following
tasks relates closely to this as well and must be done at the same time
o IP address fields in configuration file should accept mask
format as well, IP/MASK, and not just plain IP.
- o Connection classes should be actually implemented in
- serverconfig.c. They can be defined but they are totally
- ignored currently. And they should be redefined also.
+ o If client's public key is saved in the server (and doing public key
+ authentication) then the hostname and the username information could
+ be taken from the public key. Should be a configuration option!
TODO/bugs In SILC Libraries
===========================
- o See client library TODO/bugs
-
-
-TODO/Bugs in native WIN32 support (libraries)
-=============================================
-
- o 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 make install copies the symblic links from lib/silcsim/ and not
+ modules.
+
+ 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 Rewrite the lib/silcsim/silcsim.h. The SilcSimContext should be
+ private and silc_sim_alloc should take necessary arguments.
+
+
+TODO in SILC Protocol
+=====================
+
+Current protocol version is 1.0. However, it is far from being perfect,
+and needs to include additional features. Following protocol TODO entries
+describe new stuff to be added to protocol versions 1.x.
+
+ 1. Re-define the Status Payload: it is now 16 bits, split it into two
+ 8 bits fields. First field includes status types from 0 - 9 and
+ 10 - n *if* it is not an list of errors. If it is list of errors then
+ the first field includes 1, 2 and/or 3, and the second field includes
+ the error status 10 - n. This way it is possible to send multiple
+ errors (list of errors) and we have a way to tell the receiver that
+ there will be other errors as well. The second field is used only
+ if there is list of errors. If normal status, or normal (single)
+ error status the second field is set to zero, and must be ignored.
+ Hence, the status works same way as now except for list of errors.
+ To be included in protocol version 1.1.
+
+ 2. Define that WHOIS and IDENTIFY commands must send list of errors
+ if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
+ requested and was not found. Each unfound entry must cause an error
+ command reply to the sender. Also define that errors must be sent
+ *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
+ even from clients). Additional specification (or appendix) should
+ be done to define the payload and the parameters. It could be used
+ to make the WHOIS command support various search conditions as well.
+ This would be the way to extend the WHOIS command to support various
+ 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.
TODO After 1.0
not in distribution), but it is not used yet, and it requires some
tweaking on the Makefiles (we want static lib not shared).
+ o Implement the defined SilcDH API. The definition is in
+ lib/silccrypt/silcdh.h.
+
o Add builtin SOCKS and HTTP Proxy support, well the SOCKS at least.
SILC currently supports SOCKS4 and SOCKS5 but it needs to be compiled
in separately.
to start writing one myself. Anyhow, the OpenSSL X.509 lib should
be checked.
- Other package that should be checked is the NSS's X509 library.
+ Other package that should be checked is the NSS's X509 library,
+ which I like more over OpenSSL package.
- o SSH2 public keys support. Maybe - not really needed but could be
- nice as SSH is widely used all over the place. SILC Protocol
- supports SSH2 public keys.
+ o SSH2 public keys support.
o OpenPGP certificate support.
projects / silc.git / blobdiff